The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can I lock or hide fields on a screen based on user?

Deleted user
May 28, 2014

I have a field on a screen called "DA Priority" that I use for fine tuning priority of issues. I have it defaulting to 0, but the users could change it when they are creating a new issue which i want to prevent.

Is there a way to lock or hide this field for all users except a select few

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
May 28, 2014

Jira doesn't do field level security.

The two standard workarounds are Quisapps field security plugin, or to take the fields off "edit" or "create" screens and only allow them to be changed during transitions (Which you can protect with workflow conditions)

Deleted user
May 28, 2014

I dont see that plugin when searching the marketplace addo-ons.

As for yor 2nd suggestion, i think that is getting a bit too complicated for me.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
May 28, 2014

Oops, sorry, I didn't notice the OnDemand tag. Quisapps field security isn't available to OnDemand users. I'm afraid you're stuck with the hard way.

TAGS
AUG Leaders

Atlassian Community Events