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; } } }

Only a particular group can create an issue

Marta CRUZ MEGI

Hi i'd like to know how to customize the workflow in order to restrict the creation of one type of issue to a particular group.

for example: the task in my project "X" only can be created by the developers group

the rest of issues can be created by anyone

thanks in advance

Accepted answers

Nic Brough -Adaptavist-

You can't do this cleanly. If a user has "create issue" permission, they can create any issue type in your project.

If you were on Server, there are a couple of add-ons or hacks that can sort of prevent it (but they are easy to bypass).

On both server and cloud, it should be possible to set up a workflow such that the create process will fail a validator based on the groups the user is in, but this is very ugly for the user because they still get to select the "wrong" issue type, and can lose all the data they enter into it.

All comments

Nic Brough -Adaptavist-

You can't do this cleanly. If a user has "create issue" permission, they can create any issue type in your project.

If you were on Server, there are a couple of add-ons or hacks that can sort of prevent it (but they are easy to bypass).

Marta CRUZ MEGI

thanks a lot for your quick answer. then it is not possible? how can a develop the "ugly" solution?

but. for example if i want that the group "PruebasMarta" can modify an issue in an status (for example in progress), in this status i add a new property:

jira.permission.edit.group= PruebasMarta ,
but i don't know which is the command to avoid or allowed the creation because if I try
jira.permission.create.group.1= PruebasMarta it doesn't work

Nic Brough -Adaptavist-

Workflow properties are a nice idea, but they don't work for create, because you need the property to exist before you create the issue. Which you can't do, because there's no issue with a status to put it on yet.

I'm not sure how I'd create a "failed" validator on Cloud, I think you need one of the standard ones from a free add-on.

Marta CRUZ MEGI

thanks a lot for your help

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud