How to Restrict Editing of Assets Field (Insight) to Only Project Administrators in Jira Cloud?

[Antony Vijay]

Hi Everyone,

I need to restrict editing of an Assets (Insight) field in Jira Cloud so that only users in the project role “Administrators” can change its value.
All other users should not be able to modify or select any object in this field on Edit/ View screens.

I tried:

• ScriptRunner Behaviours, which works for regular custom fields, but doesn’t work on Assets fields because they are not supported in the Behaviours supported‑fields list. [marketplac...assian.com]
• IQL filtering, but it can only filter objects, not control who can edit the field.

Is there any supported way in Jira Cloud to make an Assets field effectively read‑only for non‑project‑admins?
Or any recommended workaround?

Regards,

Antony

[Victor Law - Ricksoft]

Hi @Antony Vijay

Welcome to the community.

Perhaps you can consider adding a workflow transition screen with a condition restricted to the project admin role.

https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/#Conditions

Thank you.

[Trudy Claspill]

Note that Transition screens are possible only in workflows for Company-managed projects.

https://support.atlassian.com/jira-cloud-administration/docs/map-a-screen-to-a-workflow-transition/

[Arkadiusz Wroblewski]

There isn’t a native, supported way in Jira Cloud to make one specific field (including an Assets / Insight object field) editable only for the project role “Administrators” while leaving the rest of the issue editable. Jira permissions (Edit issue) are issue-level, not field-level, and Assets fields aren’t supported by ScriptRunner Behaviours on Cloud for this use case.

Supported workaround (Company-managed projects only):

Remove the Assets field from the normal Edit screen (so nobody can change it during standard edits).

1. Create a dedicated workflow transition (often a “self-loop” like Update Asset) that:
2. uses a transition screen containing the Assets field
3. has a Condition restricting the transition to the Project Role: Administrators
4. Keep the field on the View screen so everyone can see it.

That effectively makes the field “admin-editable only” without blocking normal edits to other fields.

If it’s a Team-managed project: that workflow/screen approach won’t work (team-managed workflows/screens are limited), so your realistic options are:

• use a Marketplace “field security / field permissions” app, or
• redesign the process (e.g., admins update it via a controlled step, or use a separate admin-only issue/action).

PS: Assets schema roles control who can edit Assets data / objects, but they don’t provide Jira field-level control on issue screens—so they can help limit who can interact with the Assets side, but they won’t fully enforce “read-only field for non-admins” in Jira by themselves.

[Rilwan Ahmed]

Hi @Antony Vijay ,

1. Permissions to Assets are granted based on Asset roles and not project roles. You need to add required users to group and then map it to required Asset roles.
   https://support.atlassian.com/assets/docs/add-users-or-groups-to-an-object-schema-role/
   Workaround:
   For example, if you have a project key named ABC, you can create a new user group and name it like abc-admins, and add required users to it. After that, map this group to project admin role in space settings and also Assets Manager role in Assets.
   In future, you don't need to update add/remove users in both sections, instead just add user to the group. 
2. Regarding Edit, check any of the below options work for you
   • Create an Assets object custom field and add this field to to View screen and Edit screen. Grant Edit permission on the space settings only for project admins. 
   • Add jira.issue.editable properties in status.
     https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/ 

[Antony Vijay]

Hi @Rilwan Ahmed

Thanks for the suggestion! I appreciate the idea of using workflow properties.

However, workflow properties apply at the issue level, not at an individual field level. This means they control whether the entire issue can be edited, but they cannot make only a specific field read‑only while leaving all the other fields editable.

In my case, I need only the Assets (Insight) field to be non‑editable for non‑Admins, while allowing all other fields on the issue to remain editable as usual. Since workflow properties don’t support field‑level edit restrictions, this approach unfortunately doesn’t meet the requirement.

[Rilwan Ahmed]

Hi @Antony Vijay ,

You can use  permisison property Which will allow edit permisison only to given group or role. It is not possible to restrict edit permissions to a specific field only for a group/role  using only native Jira workflow properties. 

jira.permission.edit.group = group_id
jira.permission.edit.projectrole = project_Role_Id

Regarding Behaviors, I suggest you to contact the plugin vendor directly for the suggestion.
https://marketplace.atlassian.com/apps/6820/scriptrunner-for-jira?tab=support