Setting user/group permissions on a custom field in JIRA

[Anton Marinov]

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:

http://confluence.atlassian.com/display/JIRA050/Configuring+Issue-level+Security

But it does not seem to address the above needs.

Thank you in advance for your help.

[Gopala krishna]

Hi All,

I am new to JIRA, and i'm using JIRA Cloud and i want to know about the field level security for different users.

Is it possible in JIRA Cloud??. Thanks in advance.

Thanks,

gopala krishna.

[Nic Brough -Adaptavist-]

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.

[Takafumi Ohtake -Ricksoft-]

Currently, there are apps that enable "field level security" for Jira Cloud.

Field Level Security Apps 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.)

[Ramiro Pointis]

Hi Anton,

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:

http://confluence.atlassian.com/display/JIRA043/How+to+create+a+new+Custom+Field+Type#HowtocreateanewCustomFieldType-Admin-onlyeditablefield

Or here it is a plugin you can install in case your on Standalone version:

https://plugins.atlassian.com/23216

[Ramiro Pointis]

Here it is a discussed solution for this:

http://forums.atlassian.com/message.jspa?messageID=257297780

[Marc Nollet]

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?

[Sudipta Panda]

How this is going to work in current new jira issue view? :)

[Nic Brough -Adaptavist-]

Exactly the same way - the new view still stops you editing fields if they're not editable, and it pops screens during transitions.

[Olga Buslovich]

Thanks Nic Brough!

Would you give an example on how to make " ... 'edit field X' a workflow action instead of an edit (and adding conditions to the transitions you add for it)" in JIRA cloud , please?

Thanks in advance ,

Olga

[Nic Brough -Adaptavist-]

• Remove the field from the edit screen.
• Create  new screen that has the field you want to protect.
• Edit the workflow, adding transitions to each status.  These transitions should
  
  • Have the screen with the field on it
  • Go back to the same status
  • Have conditions that only allow people you want to edit the field to use them

[Olga Buslovich]

Thank you so very much, Nic Brough!!

Adding a new screen that includes the field that I want to restrict access to, adding a new transition with the condition that only a few users can change entry of that field did the trick.

Thank you again,

Olga

[Ahmet Kilic _catworkx]

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

• Have conditions that only allow people you want to edit the field to use them
• How can I do this exactly?
• On Postfuntion I used 

• Precondition: User Is In Any Roles (JSU)

• But it didnt work out

Thanks in advance

[Nic Brough -Adaptavist-]

Why are you using post-functions when the solution specifically said to use conditions?

[Rotem Shani]

Hi,

I have almost same question,

In my case we use Jira Could and I would like to change permissions for Priority field so only admin can change it.

Is it possible? 

Thanks,

Rotem

[Nic Brough -Adaptavist-]

It's the same answer as before, it's not changed.  Jira doesn't have field level security.

[Rotem Shani]

Thanks 

[raphilevine]

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.

[Thienky Dang]

This answer by Ivan Tovbin seems to be the only workaround. Not too much work if its truly required.

[Procurement]

Hello,

I am facing similar issue as Marc Nollet.

Please help with solution.

We need only one customer field to be edited by specific group and rest should be read only.

Thank you.

[Lucas Silva Dummy Account]

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