Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Configure field security permission


Is if possible to configure or restrict users that don't belong to certain role from editing certain fields on Issues?

For e.g. User in Quality role can only edit "Defect Comment field"

Users in Logistics shouldn't be allowed to edit "defect comment feild"



Any reference link will be very helpful... I'm using JSD Cloud.


Thanks for help


1 answer

1 accepted

2 votes
Answer accepted

Jira does not have field level security.

The best you can do is move it into the workflow (so people have to use the workflow to get to edit fields, and the workflow can have "conditions" that can protect the edits)

Thanks @Nic Brough _Adaptavist_ 

I'm looking for a reference article / implementation example, if you are aware of any please share... thanks

I've used conditions in WF for roles but not sure how can field be implemented.

Ok, so if I were to do this from scratch, I would

  • Choose my field that I want to protect.  Let's call it "Pet-type"
  • Create four new screens (making liberal use of copy), with names and content such as:
    • Screen-c: Has all the fields I want the users to give me when creating an issue (maybe including pet-type)
    • Screen-e: Does not have pet-type on it
    • Screen-l: Definitely has pet-type on it
    • Screen-T: Has only pet-type on it
  • Then you set up a screen scheme that says
    • Create: Screen-c
    • Edit: Screen-e
    • View: Screen-l
  • And use that in the issue type screen scheme for whatever issue types you want to protect pet-type for
  • Now edit the workflow, and for every status that you want to allow edit of pet-type in, add a transition that goes back to the same status with:
    • Name: edit pet-type
    • Screen: Screen-T
    • Condition(s): Only group or role X can use this transition

You'll now find that people who match the condition can "edit" the pet-type.  Downside is it litters the history with "status changed" when it didn't, and you have to tell your people to look in the workflow for editing it.

Like S likes this

Thanks @Nic Brough _Adaptavist_ its a good curve ball!

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

189 views 1 6
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