Can we create a user specific custom field in Jira Cloud?

[Vishnuvardhan Reddy]

Hello,

We have a ask that requires to create a custom field which can be updated by only a particular user. So, is there any way to create a Custom field that might give user or role specific permissions to update the field?

Thanks in advance.

[John Funk]

Hi Vishnuvardhan,

There are some third party apps that would make that fairly easy. But what I do is create the custom field but do not add it to Edit screen. (You will need at least an Edit screen and a Create/View screen or all 3 separate screens on the project). 

Then create a self looping transition on the Status (or statuses) in your workflow. Attach a screen that only includes this field. Then add a Condition to the self-looping transition to only allow that user to execute. 

This is a bit clunky but it works. (But just a note, if the user can do Bulk updates (and knows how to do that), they can still update the field. 

[Victor Law - Ricksoft]

Hi @Vishnuvardhan Reddy

It is not doable natively in Jira as there is no field-level security or permission. However, it is possible to set the specific field in a transition screen and set the condition that restricts a particular user from viewing that information, as suggested by @John Funk. With this approach, it might not be hard for the user to notice that such information is included in the Jira issue/work item.

Alternatively, you may consider Secure Custom Fields for Jira, developed and maintained by my team at Ricksoft. This allows you and your team to set the field value to be visible to specific users, user groups, or project roles. Additionally, it supports various Jira field types. Please feel free to submit a request to us if you would like to try out the app and request any further assistance with setting it up.

Thank you.

[yqiao]

In Jira, field-level permissions (the ability to restrict editing of a specific custom field to only certain users or roles) are not supported natively in Jira Cloud or Jira Data Center/Server.

I think we can try with some workarounds:

1. Use Workflow Transitions with Conditions

• You can create a workflow transition that updates the field and restricts that transition to a specific user or role.

• However, this only works if you want the field to be updated at a specific point in the workflow, not at any time.

2. Use Field Configuration to Make the Field Read-Only

• You can make a field read-only for everyone (not selectively), but not editable for only one user/role.

3. Marketplace apps

• Field Security for Jira