Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How can I have ONLY admin users to be able to change 'Priority' field?

How can I have ONLY admin users to be able to change 'Priority' field? For rest of the users, the priority field need to be disabled and cannot be changed.

1 answer

0 votes
Tuncay Senturk Community Leader Nov 21, 2019

Hi @Janesh Surti 

You can do that using some workflow tricks.

You should follow below steps:

  1. Remove priority field from issue edit screen so that no one can edit the issue to change issue's priority. But you can still create issue with priority field if it is in Create issue screen.
  2. Add transition to from any status to the same status where you want to allow changing priority (e.g. transition from In progress to In progress). Add a transition screen for this transition and add Priority field to the screen. You can name the transition as Edit priority.
  3. Add a workflow condition in which you allow specific users, groups or roles (e.g. Admin) to use this transition.

We used this approach many times for our clients. I hope it helps.


Thanks Tuncay.

We wanted to figure out a way to disable the 'Priority' field for all users (except few) when creating an issue (through create issue screen). The 'Priority' field should be visible (not hidden) and should be disabled for general users when they create an issue or view an issue.

Tuncay Senturk Community Leader Nov 21, 2019

Then you should use Behaviours app and write some script to make it read only. There is no out-of-box solution for  that 

Hello @Tuncay Senturk Is there a way where the 'Priority' field can be enabled during creation/logging of the Jira story, but once the story is created, only certain users are allowed to modify the 'Priority' field. Not even reporter of the Jira story should be allowed to modify the priority, except those few assigned users. Any insights into this is much appreciated.

The original answer tells us how to do that.  Could you explain where you are stuck on implementing that?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events