Similar discussion was had yesterday - see https://answers.atlassian.com/questions/45948115
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not sure they answer my question because in the response,"In the post-function of the "create" transition of the issue workflow you can add validations to check if the user belongs to the group which can create the task issues or vice-versa" The way permissions are broken down is if a person can create an issue type, he can create ALL issue types including Epics. We want to limit a group to create all BUT Epics. If this can happen "out of the box" then fine but if programming or scripting is involved then it might not be a viable solution for us.
Please advise.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that's the point of the answer. Off the shelf, you can't configure this - if a user can create, they can create. But you can set up a workflow that fails a validator and hence stops someone creating a certain type.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There aren't any. What you want is to check that the user matches a group. I don't know if there are validators available on Cloud that can do that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Nic Brough -Adaptavist-
I use the validator user in the field (reporter) should be at least in one of the project roles (admin, PM) on the create issue . It worked for jira server.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
[Jira Software v7.5.3]
Hi all,
looks like this is exactly what I need!
As far as I understand, the settings need to be done in "Project settings - Issue types - Epic", then edit the transition "create" in epics workflow.
Unfortunately I cannot find any corresponding setting neither in "Validators" nor "Post Functions". Validators only allow:
I tried "Issue Matches Structure Query", but cannot lay hold on reporters role with a query ...
Could you please explain, which setting you used to achieve e.g. only jira-administrators can create epics?
Many thanks in advance
Regards
Uli
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.