nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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?

Accepted answers

Jayesh Raghuvanshi_qb6277

@Marcelo Viana de Siqueira

No, there isn’t a native per–issue-type “Create” permission in Jira Data Center; the Create Issues permission applies to all issue types in the project. The supported built‑in workaround is to give the restricted issue type its own workflow and add a Permission validator on the Create transition that only group ABC can satisfy.

My suggestion:

Workflow scheme: ensure Task uses Workflow A and Bug uses Workflow B
Edit Workflow A (Task) and select the Create transition; open Validators and Add validator → Permission validator
Choose a permission to check that you can safely restrict, for example: Set Issue Security, Administer Projects, Delete All Comments, or another permission that regular users do not need day‑to‑day
Update the project’s Permission Scheme so only group ABC (and admins) have that specific permission; publish the workflow

Thanks
Jayesh R

All comments

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.

Jayesh Raghuvanshi_qb6277

My suggestion:

Workflow scheme: ensure Task uses Workflow A and Bug uses Workflow B
Edit Workflow A (Task) and select the Create transition; open Validators and Add validator → Permission validator
Choose a permission to check that you can safely restrict, for example: Set Issue Security, Administer Projects, Delete All Comments, or another permission that regular users do not need day‑to‑day
Update the project’s Permission Scheme so only group ABC (and admins) have that specific permission; publish the workflow

Thanks
Jayesh R

Marcelo Viana de Siqueira

Hi @Jayesh Raghuvanshi

Thanks a lot for the detailed explanation, that approach works perfectly with native Jira Data Center features.

Here’s what I did based on your suggestion:

Created separate workflows for Task and Bug issue types.
Edited the Task workflow and added a Permission Validator on the Create transition.
Selected the Edit All Comments permission for the validator.
Updated the project’s Permission Scheme so that only group ABC (and admins) have this permission.
Now users in group ABC can create both Tasks and Bugs, while users in group XYZ can only create Bugs.
It’s a clean, fully native solution (no apps required).

Thanks again for the tip!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

jira-data-center

data-center