Is it possible, either out of the box or through a plugin, to restrict who can edit labels and other specific fields even though that person might have overall edit rights to an issue?
Thanks.
We needed a similar restrictions for the fix version/s field, so my solution was this:
- Hide the field from the standard edit issue screen
- Create special global transitions for changing it; these transition has a special screen, just with the field, and a condition of 'user is in group X', so that only users in the specified group will be able to see and use these transitions.
Unfortunately, once we upgraded to JIRA 6, the inline-edit feature ruined everything; anyone with the appropriate issue permission can edit this field now (since, as a system field, it's always displayed).
Security is at the issue level, not at field level. You can ,however, using javascript, make fields read-only, but this is not a security solution.
There's a plugin that promise you that, https://marketplace.atlassian.com/plugins/com.quisapps.jira.jfsbut I do not tried it, nor I know if it has support for labels.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.