Forums

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

How to restrict Editing of Issues for particular Users/Groups/Roles in a particular Step?

CK1
Contributor
March 12, 2012

Hello all,

What I'm trying to do, is to basically lock down an Issue for certain users in a particular step (more fine grained than the vanilla "edit permission").

Alternatively, is it possible to configure permission specific "edit" screens, so I could hide some fields (this would also be great for reducing clutter for some users) ?

I think I saw something to that end, but after a whole day searching through Jira documentation I can't find it anymore...

More than happy for some input or links (hacks, plugins also welcome - If I overlooked some standard functionality, I'm sorry. New to Jira)

Thanks in Advance

V.

3 answers

0 votes
Tansu Kahyaoglu
Contributor
January 20, 2013

You can use following javascript code https://answers.atlassian.com/questions/38542/how-to-check-if-the-login-user-is-a-jira-administrator-using-a-rest-call/38727

Just change "alert('admin')" part with jQuery('#your_customfield_id').hide()

or set enabled false using jQuery

0 votes
Jo-Anne MacLeod
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 Leaders.
March 12, 2012

The behavious plugin will allow you to show/hide fields. Check it out.

For the requirement of restricting editing. I am just testing that exact requirement. If it works, I'll have a solution for you in a few hours (when I get around to testing it).

0 votes
Stephen Hayden
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 Leaders.
March 12, 2012

Could maybe see doing some of what you're describing by using security, and changing it with post functions on certain transitions to change the groups/individuals that can edit. It doesn't sound like that might quite get the functionality you want though.

Loosely related to you question, I often accomplish some of this by using tabs on my default screen, so that those who need information that isn't applicable to all can go to their tab. It doesn't prevent them from editing, but it does clean up the default screen and make JIRA (in our use case at least) more usable.

Suggest an answer

Log in or Sign up to answer