You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi Atlassian Support team,
I have a question regarding some JIRA functionality and was hoping you could help me.
Is it possible in JIRA to set up permissions, so that I can have a Group or list of users only that can edit a Custom Field value. We have a custom field, called Work Bucket, and I would like to set it so that only the PMO group in our JIRA instance can set the value in this field. Or it can even be so that only this Group can see the field, whatever is possible.
Can you help me understand if any of the above is possible and how do I do that?
I tried this page:
But it does not seem to address the above needs.
Thank you in advance for your help.
There is no "field level security" in Jira.
You can control editing to an extent, by making "edit field X" a workflow action instead of an edit (and adding conditions to the transitions you add for it), but you can't hide a field at all.
On server, the Quisapps field security app is the best solution, although Scriptrunner behaviours can hide stuff too (if you don't mind it coming out in the raw html and just being hidden by the browser - the users can override that if they want). You do not have those options on Cloud.
Currently, there are apps that enable "field level security" for Jira Cloud.
Hide fields and make fields read-only based on user, group, project role, and so on.
(Please note that I'm one of the folks behind Ricksoft that is the vendor of one of the apps.)
The most of this forum users are not from Atlassian, just to clarify.
Regarding to the documentation that you checked, that's only for give to the issue a security level so it can be visible only for the people that you want.
In order to restrict the modification for the custom field here you have other options:
Depending on your Jira Version:
Or here it is a plugin you can install in case your on Standalone version:
Hello Ramiro, I have a similar request as the one from Anton: In our organisation we use Jira 5.2.11. and we have different projects for the different teams (HW development , SW development, ...) . People from the HW development team want to add a field in the SW development project issues to be able to flag the issues as important for the HW team. This is possible but the problem is that we need to give the HW people read/write access to the issues in the SW project. This implies that the HW people can edit all the fields in the SW issues which is not preferable. What we are looking for is how to create a field in the SW project issues project that can be read/write for the HW people while the rest of the fields remain read only. Is that possible in a simple way?
Exactly the same way - the new view still stops you editing fields if they're not editable, and it pops screens during transitions.
It doesn't work for me,
I'm doing somewhere somthing wrong maybe.
2 screen I've
One for admin and other for customer
By creating there is no option to go back transition
|Precondition: User Is In Any Roles (JSU)|
Thanks in advance
Why are you using post-functions when the solution specifically said to use conditions?
It's the same answer as before, it's not changed. Jira doesn't have field level security.
I too need this ability.
There are certain fields (both custom and native) which only certain users (i.e. Developers) should be able to edit and some which we don't want to even display to some users.
I am on Jira Cloud and it seems that this is basic functionality which is missing.
Hi, you can do that with the the jira field security plugin https://marketplace.atlassian.com/plugins/com.quisapps.jira.jfs the only problem is that this plugin only sets the security clearence for custom fields