Is it possible to adjust field edit permissions without using a separate screen?

[Grant Olson]

I'd like to be able to restrict edit permissions on custom fields in our Jira instance such that only a select group of users can edit these specific fields.

I am aware of the global looping transition + use of a separate screen in the workflow but as far as I can tell this prevents the ability to easily edit the field without having the extra clicks to go into the screen from the issue detail view. I'd like to have the allowed users be able to quickly edit/bulk edit the field without having to take those extra clicks for each separate issue needing editing. E.g., we use JXL Sheets in our instance to bulk edit fields often but with the looping transition workaround I mentioned above this doesn't work...

I also see there are some Marketplace apps that can set permissions for fields but my question for those would be: can you use one of these apps to modify the permissions on an existing field, rather than having to create a new "secure" field made via the app?

Any insight into my question is appreciated. Maybe I am missing something here? Thank you!

For added context: Example of the "global looping transition + use of a separate screen" workaround I refer to: https://community.atlassian.com/t5/Jira-questions/how-to-restrict-a-users-for-custom-field-in-jira/qaq-p/2232028

[Aaron Pavez _ServiceRocket_ · Accepted solution]

Hi @Grant Olson 

> I'd like to be able to restrict edit permissions on custom fields in our Jira instance such that only a select group of users can edit these specific fields.

Sadly Jira doesn't have field permissions. You need a plugin for that.

And going the way Valerie mentioned/and you mention is the other only way to restrict fields.

Regards

Aaron

[Grant Olson]

Thank you, Aaron, appreciate you providing answers here as well.

I'll explore the plugin options.

Shame that Atlassian doesn't have field permissions - hopefully this is something that can be introduced in the future.

[Valerie Knapp · Accepted solution]

Hi @Grant Olson , thanks for your question.

Would a possibility be to limit the people who don't need to edit to have only 'browse permission' to the project? In this way, the people who need to create, assign, etc, can maintain the ease of use and people who should be more like informed stakeholders can still maintain visibility without an over-engineered solution involving transition screens.

I think the alternative, as you say, would be to get an app. There are several that do this kind of thing but there is the cost and the configuration to consider. https://marketplace.atlassian.com/search?query=field%20permission 

Please share your feedback about the project permissions.

Best wishes

[Grant Olson]

Thank you, Valerie, appreciate your answers here. In our case, we need people involved in the project to have edit rights to most fields, so unfortunately changing the project permissions won't be a solution. I'll take a look at the app options!