Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Restrict user to edit a custom field

Ashish Saini
Contributor
March 25, 2022

Hello Community, 

I wanted to take some advice on restricting edit issue action on a custom field by certain individuals or group of users

Is it possible to achieve on cloud using native or by using any add on 

Please share your thoughts

Thanks in advance 
Ashish

1 answer

1 vote
Ste Wright
Community Champion
March 25, 2022

Hi @Ashish Saini 

Natively, there isn't field-level permissions - just project-level (i.e users either have edit, or they don't).

Not that it's impossible - there are...

  • Workarounds - I sometimes see teams add the field to a separate screen, and use the screen during a workflow transition. Then use a validator to limit who can use the transition (i.e those users who need to edit the field).
  • Automation - use Automation to manage things - for example...
    • Create an Automation rule based on a Group - if a user is in the Group, modifying the field is fine. If the user is not in the Group, then the field reverts to blank after editing and alerts the user they are unable to edit this field
    • Make the field view-only, then add a second custom field. If a user in the Group enters a value, then it updates the official field. If not, the official field is not modified (effectively avoids the need for blanking in the rule above).
  • Apps - Apps like Secure Custom Fields for Jira might be able to help

It'd be good to get your thoughts on the options above, whether any sound of interest, and if you need any help with implementing any option - let us know more specifics about why you need this, and what the rules should be!

Ste

Ashish Saini
Contributor
March 25, 2022

Hi @Ste Wright : Thanks for the response

We are developing a process basically and want to restrict certain users from editing a custom field in jira.

Users from certain group should only modify the field in jira.

We have integrated Jia with another external tool ...when the users update the value in external tool it should update in jira ..

I tried using secure custom field ..was able to restrict on jira level 

however , when the sync happens between 2 system it is not updating the secure cutom field ..i believe due to an extra prompt it has when we try to update it from UI 

 

Any thoughts please 

Regards
Ashish

Ste Wright
Community Champion
March 25, 2022

Hi @Ashish Saini 

In your scenario, I think what I would do is use one of the two automation options - as it would allow you to prompt users to use the external platform where necessary.

Do you think either of those options above would be acceptable?

Ste

Ashish Saini
Contributor
March 25, 2022

Hi @Ste Wright : In smartsheet we can only set 1 sync flow per sheet.

Any script can you suggest script runner or SIL to restrict certain users from editing the field.

Regards
Ashish

Ste Wright
Community Champion
March 25, 2022

Hi @Ashish Saini 

Not that I know of - Scriptrunner uses Behaviours for this, but those aren't available in Cloud.

You could try asking a vendor directly though for more expert advice? For example, contact Scriptrunner using the support options on their Marketplace listing.

Ste

Rinat Mizrahi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 15, 2022

@Ste Wright  

Can you please share what action should I configure on automation in order to revert editing field if the user is in the group I want to limit?

Pedro Webster February 6, 2023

@Ste Wright 
Could you please send me a example of the automation below?

  • Automation - use Automation to manage things - for example...
    • Create an Automation rule based on a Group - if a user is in the Group, modifying the field is fine. If the user is not in the Group, then the field reverts to blank after editing and alerts the user they are unable to edit this field
    • Make the field view-only, then add a second custom field. If a user in the Group enters a value, then it updates the official field. If not, the official field is not modified (effectively avoids the need for blanking in the rule above).
Like Eloise Lyons likes this
Eloise Lyons
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 16, 2023

@Rinat Mizrahi

@Pedro Webster 

@Ashish Saini 

There is a workaround documented for cloud which will reset the value of the custom field if the user is not apart of a particular group (essentially restricting the specified custom field):

https://confluence.atlassian.com/jirakb/how-to-revert-a-custom-field-value-when-edited-by-unauthorised-users-using-automation-1167831117.html

Suggest an answer

Log in or Sign up to answer