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

Authorizations of set of users to change only certain fields

In the issue only particular group can edit the certain  custom fields . how can we achieve this.

2 answers

1 accepted

3 votes
Answer accepted
John Funk Community Leader Nov 30, 2020

Hi Reddy,

There is a bit of a work around to handle that. 

First, you would need to create a separate Edit screen for that project if there is not one already. If there is one, edit it to remove the fields that you want to control the update for. 

If you create a new Edit screen, just copy the existing screen and remove those fields.

Then create a new Transition screen - it's really just a regular screen that you are going to use with a Transition in the workflow. 

For this new Transition screen, only put in the fields that you want to control (that is, the ones you removed in the Edit screen. 

Then edit the workflow to add a new looping Transition to the appropriate status. A looping transition is a one that simply goes from the status back to the same status. 

Then edit the new Transition in the workflow to add the Transition screen to that Transition. Place a condition on that transition so that only group you have identified can execute that transition and thereby edit the fields. 

This is the official Atlassian approach to field-level security. Many admins have found that plugins such as ScriptRunner with its Behaviors feature gives more flexibility and ease of customer usage for this case.

1 vote

Hi @reddy dumpala 

There is no per field permissions in Jira. Follow the solution provided by @John Funk above to achieve that.


Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,104 views 8 28
Join discussion

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