Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Restrict permission to add comment and other fields like labels, status etc. when Issue Type change

James Khow
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 26, 2020

My current Jira is having an Issue Type as Bug and all developers can add to comment, change labels etc. However, I want to restrict the developer's ability to comment, change the status, category etc. once the project manager moves it to Service Request instead of Bug. How can I do this? 

1 answer

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 27, 2020

If you have a different workflow for Bug and Service Request, you can do this with workflow properties.

Assuming they currently have the same workflow, then I would copy the current workflow and rename the copy to something like "limited service request".  You can then add Workflow properties  to each step, limiting the permissions with properties such as jira.permission.edit.group=project-manager   That will work for most project permissions, but for "change status", you'll need to add "conditions" to the transitions in the workflow.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events