Allow bulk edit using REST API without allowing users to edit

[Patricia Paguio]

Hi,

I know this is a big shot in the dark, but does anyone know a way I can allow REST API to bulk edit issues without allowing users to edit the fields?

I have fields that will need to be updated using the REST API but should not be allowed by the users to edit. However, I know that the REST API allows the edits of issues if it is on the edit screen.

Is there a workaround I can implement so that users cannot edit some fields even if it's on the edit screen? Or is it somehow possible to edit via REST API without having the field in the edit screen?

Thanks in advance!

[David Bakkers · Accepted solution]

Sorry, but Jira doesn't have field level security. You could make a custom screen scheme for that project that only displayed certain fields, but it would still apply to everyone. You can't dynamically switch between screen schemes per project based on a user profile.

However, there are some third party add-ins that provide field level security, but only for custom fields. Read this article for more information on the same topic.

[David Bakkers]

Nope. Once a user accesses the REST API with their credentials, they have equal permissions to change data as if they were logged into the web interface. If you remove the field from the edit screen to block the REST API's access, you block the same access in the web interface too.

[Patricia Paguio]

Ahhh, I see. Is there a way then to allow only users in certain project roles to edit all fields in an edit screen, but prevent users to edit some fields in the edit screen?

For example, is it possible that me as an Admin should be able to edit all fields in the edit screen so I can allow REST API with my credentials to edit these fields. But then prevent those in the Developer role access to edit half of the fields in the edit screen?