How to limit user role ability to create and edit certain issue type?

[Inna S]

Hi,

Let's say we have a project that holds all product group issues: Initiatives, Stories and Bugs.

Only PMs are allowed to create and manage Initiatives, but not Stories. 

Only Developers are supposed to create and manage Stories, but not Initiatives.

And everyone can create Bug, but only QA can close it.

I understand that Jira does not allow for this level of granularity and came across the suggestion to use security scheme making the issues 'read only' for certain groups.

Came across the following suggestions: 

* based on workflow status and user group or role https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status

* using scriptrunner https://community.atlassian.com/t5/Jira-Software-questions/Restricting-issue-creation-of-certain-issue-types-based-on-user/qaq-p/821331

* using security schemes to make certain issue types read only https://confluence.atlassian.com/jirakb/how-to-set-certain-issues-be-read-only-to-certain-groups-roles-776820639.html

What is the currently recommended, easiest way to achieve the requirement in Jira Software Cloud?

Thank you

[Sam Nadarajan]

Hello @Inna S ,

I've used and like Scriptrunner behaviours, unfortunately, behaviours are only available on Jira Server/DC, so you wouldn't be able to use that functionality in Cloud.

There's an open issue here that you can vote on to add this functionality. Note in the comment thread that you can restrict the creation of issue types based on roles in team-managed projects.

[Inna S]

Thank you, @Sam Nadarajan .

The suggestion is from 2015, and judging from the others I've encountered so far, this basically means it won't be done. They have a request for boolean custom field sitting there for 18 years. 

[Sam Nadarajan]

It's a hit or miss sometimes, but Atlassian does monitor these tickets. It does partly depend on public opinion - i.e. # of votes.

[Pedro Felgueiras]

Hi @Inna S 

From my experience, Script Runner is the best tool to archive this kind of requirement. 

You need to create a scripted condition that checks if the users belong to X role in order to create. The code is in groovy, there's a lot of examples on the internet and it's very easy to read 

[Inna S]

Thank you, @Pedro Felgueiras , @Sam Nadarajan just wrote this is not available in the Cloud version.