how to restrict a users for custom field in jira

[suren]

We have custom field called " Sprint #".

Got a requirement from product team that field tagging/updating should be restricted for x,y,z members alone.Kindly help me to work on this!

[Alex Koxaras _Relational_ · Accepted solution]

Hi @suren 

• You have to remove the field from the edit issue screen
• Then you have to create a screen with that field inside
• Create a self transition within that workflow
• Add a condition on that transition that only these members, or this group can transition the issue, meaning edit that field

Hope that helps.

[suren]

Hi @Alex Koxaras _Relational_ ,

    Creating a new screen will affect the older issues?, if I'm wrong can you provide a screenshot for these process,I mean which you have suggested above.

[Nic Brough -Adaptavist-]

Yes and no.

It will affect the issues when someone uses the new transition.

But it will not change the existing data you have on the issues.

[Alex Koxaras _Relational_]

@suren the above steps are pretty much standard Jira functionalities that you have to learn (and which I suggest you learn them). This will help you understand better how Jira works and you will be able to troubleshoot future problems. 

• For the first two bullets read this https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-screens/
• For the 3 bullet read this https://community.atlassian.com/t5/Jira-articles/How-to-create-global-looping-transitions-in-a-Jira-workflow/ba-p/1135968
• For the conditions read this https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/

[Mattia _bitvoodoo ag_]

Hello Suren

Your request is older and you have probably already fulfilled the requirement for your custom field.

Perhaps new Jira users are facing a similar requirement. There is an easy way to create custom fields and grant the view and edit permissions with the help of Marketplace apps.

For example, our Confidential Fields app allows you to create the required fields for the various use cases and restrict sensitive information to the desired circle of users.

Best regards,
Mattia