Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Permission based on role and issue type

Hi all,


I have a Jira project with different issue types: Incident, Task and Bug. If the issue is an Incident, anyone can update any field. If the issue is a Task or Bug, some fields cannot be modified anymore by the Role "Requester" but all fields can still be updated by the role "Development". I am unable to setup this scenario in Jira... Is this possible?


I have tried to use Screen Scheme but when I restrict updates per issue type (Tasks and Bugs) it does not differentiate the role and no one can edit anymore. I also tried to use Permission schemes, which I am able to grant/deny access per role, but not per issue type. It's kind of a cyclical problem.


Note: I am using a classic Jira project.


I am sorry beforehand if the solution for this problem was already shared. I have spent a fair amount of time trying to find it but no success.


Thank you!

1 answer

1 accepted

0 votes
Answer accepted
John Funk Community Leader Apr 20, 2021

Hi Walter,

There is no way to do field level security like that in Jira Cloud.  At least not out of the box. 

But a workaround might be to remove the field from the Edit screen for the project. Then create a new Transition screen with the field showing on this screen. 

Then create a new transition on the status that loops back to itself (called a Looping Transition).

Then attach the Transition screen to the new looping transition in the workflow. 

Then you can place conditions on this transition to control who can execute the transition that shows the screen with the field to be edited. 

Hi @John Funk ,


Thank you very much for your reply.


About the workaround, considering that transitions are used to change the status of the issues, does it mean that people will only be able to update fields if they use the status button and then the popup screen?


Going the other way round to solve the same problem, do you know if there is a way to abort issue updates via Automation or any other feature? So, the user could have access to the fields but the changes would be discarded.

John Funk Community Leader Apr 21, 2021

Yes, that is the only way I am aware of to control the edit of fields for just certain people. 

The is no other way to provide only certain users with the ability to access certain fields. 

Thank you for your support @John Funk .

Like John Funk likes this

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

206 views 2 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you