Set Edit permission for specified issue type

[DW]

Hola wong,  

We have a case there is  should set specified of group only that can edit a specified issue type, for example

• Only administrator group / admin project role can edit Story or Epic issue type
• Only Jira Software users group can edit Subtask level issue type 

---

• I was try to use workflow but i discovered if workflow just work to handling transition process between status.
• i was try Jira security Scheme but it seems only for view permission set.
• i was try permission scheme, but im just see edit options its for all issue type, cannot be spesific

Is that jira can handle that ?

Any help will appreciate :)

[Diogo Teles]

Hi @DW ! 

From what I have tried so far, even with permission scheme configuration, you can only give them edit all or edit none permissions. For example, if you can allow a specific group or role to edit all issues in the project that they can see or no issues at all.

I have used a workaround for this in the past. But it is not elegant.

You would need to create screens associated with the Edit action for every issue where you want this kind of granular permission. 

Remove all fields from that screen. This makes the issue virtually uneditable.

Then create a new screen for each of those issues and add to it the fields you want to be editable for that issue type. Don't associate that screen with any screen scheme.

Then, for each of those issues, create a workflow transition called "Edit issue" from Any status to Any status. Use the screen you just created as your transition screen.

Now, you can associate transition conditions to the groups or project roles that should be able to edit that issue type.

In the end, your non-editable issues will now have a "Actions" button next to the status, and if the user clicks on it and meets the condition set in your new transition, they will see an "Edit Issue" option. Clicking on it will pop up your edit issue screen, and they can then change issue fields.

I'd add a final note to this: limiting actions in Jira to influence user behaviour is not an effective approach to improving team performance unless there are security concerns. In such cases, implementing robust processes and guidelines, and offering adequate training and support, can prove to be a more viable solution.

If you still want to try this and need help with any of the steps above please let me know :) 

[DW]

yes youre right, tons of step should be done before that, become nightmare if we need to implement this to different project scheme 

Thanks anyway

[Mark Segall]

Hi @DW - You want to look into Issue Level Security

https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

[DW]

hi mark thanks for your replied, but im already read it and try but no luck, its not for edit option, just for isue viewing, CMIIW

and also im already write this on my description, that i mean is issue Level Security

• i was try Jira security Scheme but it seems only for view permission set.

[Mark Segall]

You could update the permission scheme so that the Edit Issue action is set up like this:

• Project Role: Administrators
• Assignee

It's not perfect as an admin would need to create sub-tasks and assign to the user but it would create that split. 

Another option would be to not use sub-tasks.  Move the team to another project with a very specific issue type scheme where they only get issue type x.  Then establish a process where they link their issues to the stories on the other project. In this option, you'd still be able to share the work on a single board with an updated board filter.

[DW]

the sounds like jira cant handle my case.

but thanks anyway, its seems can be alternative ways

[Mark Segall]

Yeah Jira thinks of projects as a Team.  You can create some logical boundaries, but generally the idea is that the team can be trusted not to touch what isn't assigned to them.