Restrict issue creation by issue type using native Jira Data Center features

[Marcelo Viana de Siqueira]

In our Jira Data Center instance, I need to restrict who can create specific issue types in the same project.

Example:

• Project XPTO has issue types Task and Bug.
• Users in group ABC should be able to create both Tasks and Bugs.
• Users in group XYZ should be able to create only Bugs.

I tried adding the property  'jira.permission.create.group = ABC' to the initial status of the Task workflow, but it did not work. Users from group XYZ can still create Tasks.

I also noticed that the initial transition (Create Issue) does not have the Conditions tab, only Properties, Validators, and Post Functions.

Is there a native way (without apps) to restrict issue creation by issue type in Jira Data Center?

[John Funk]

Hi Marcelo,

One option would be to create separate workflows for each issue type - even if you just copy the existing one and it is exactly the same. Then associate the workflow with the issue type in the workflow scheme. 

Then add a validator for the Create transition based on something like Project Role (you might can do this with a group also, but I don't have Data Center). If using Project Role, you can grant the role access to the group. 

[Marcelo Viana de Siqueira]

Hi @John Funk ,

Thanks for the suggestion! Unfortunately, in Jira Data Center without additional apps, the “Permission Validator” does not allow selecting a group or project role, it only checks for project permissions like Create Issues.

So it seems that with native features only, there is no way to restrict who can create each issue type within the same project. The only native alternatives I see are:

• Splitting the issue types into separate projects with different permission schemes, or
• Using Automation to delete or move the issue after creation if the user is not in the allowed group.

If anyone knows another purely native workaround, I’d love to hear it.

[John Funk]

Ouch - sorry about that. The only other thing I can think of is ScriptRunner - but not native either. Afraid there is probably not a way.