Assets object custom field not available in jira bulk edit

[MdV]

Hi * 

We use JSM with asset management und created several asset object custom fields in Jira Issues. All Jira users can modify these asset object custom fields (select the asset in jira issue). Now for some reason within issue bulk edit these Assets object custom fields are not visible or not available (greyed out). 

This means our user can edit asset object custom fields in single issues, but not for multiple issues. 

What permission is missing here? 

Thanks in advance!  

[Marc - Devoteam]

Hi @MdV 

Welcome to the community.

You are not missing permissions. It simply not possible and won't be developed.

See this issue in relation to this, JSDCLOUD-9017 

I can even understand this, as people with edit rights on the schema could create new objects or options in attributes, based on bulk updating, 

This could mess the whole assets schema and related issues.

To update assets, use the importer in assets to update or edit options in assets

[MdV]

Hi @Marc - Devoteam 

Thanks for your feedback. 

There might be some misunderstanding as we don't seek the ability for our user to update the assets or asset scheme.

We have Jira Issue types with asset object customfields. 

Every user can update these asset object customfields in any single jira issue. 

But they can't update the same asset object customfields for multiple jira issues by bulk issue edit. The field is not available in bulk edit (the user is missing the permission)

I like to understand which required permission is missing for updating asset object customfields in jira bulk issue edit. i couldn't find it in the documentation

I like to add that i as admin can update the asset object customfields in jira bulk issue edit, which proves it's technical possible with the necessary permission

[Marc - Devoteam]

Hi @MdV 

There are no permission for this.

It's not possible via bulk edit, see the related issues in my previous reply.

Atlassian will not implement this.

The only option you can explore is to run an automation rule that finds the issues based on the JQL you have and then on branching iterate over the found issues, to update the asset custom fields.

Only the lookupIssues action in automation can only do a 100 issues at a time.