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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • 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

Is there a way to make a field only editable by specified users, while being read-only to the rest?

Either customized or predefined by JIRA, is there a way to make a field only editable by specified users, while being read-only to the rest? 

For example, the Priority field being set to "Medium" by default. Then when it comes in queue, only 2 administrators of that particular Service Desk will have the option to change the field, the rest shouldn't be allowed to do so. Is this feasible? 

2 answers

1 vote
Dirk Ronsmans Community Leader Sep 16, 2020

Hi @Jillian Marabut ,

Sadly field level permissions don't exist in JIRA. (on server you could do this with behaviours  (Scriptrunner) through an addon but cloud has no such thing)

A workaround that I can think about (perhaps a bit tedious but the only one I can think of right now) would be to work with transition screens and a small "hack".

The hack:

By default if you remove a field from the edit issue screen it is no longer inline editable but you leave it on the view screen so it shows up for your agents to see. So basically a read-only field.

The Workarround (so it can be edited by your admins):

You could create a transition (with a transition screen) where you add the field on that you want to change and block that transition to only be allowed by your admins. (through a workflow property/condition)

This would look like you have a screen just to edit that field.

If this only happens initially in your process you only need 1 transition from itself to itself. If this is possible on all states perhaps a transition to a new state (like a spider/catch all status) might be an option and then you would need a manual action to move it back to the original status.

I would think this is something that can only be done initially during triage of your admins.

 

This is by far a nice and clean solution but I don't think there is any way to really block someone from changing a field if it is on the edit screen (and the users have edit issues permissions)

Hi @Dirk Ronsmans

Thank you so much for the detailed response on my inquiry. Let me try this and will update the thread if it works on my workflow. 

Thanks, again! 

0 votes
Jack Community Leader Sep 14, 2020

Hi Jillian, I would suggest looking into two methods to see which might serve you best:

  • issue security 
  • consider leveraging a specific issue type and having a unique workflow so that you can leverage the jira.permission.edit.group workflow property to each status

Thank you, Jack! Will look into this.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
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...

182 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