Custom field has a limit of 20

[Antonia]

I have created a custom field where you can search in the assets and then select assets. Is it possible to select and insert several assets at the same time? At the moment I search for an asset, select it and then I have to search and select again and this goes on and on.

Also: In the field you can only select 20 assets “This field is configured to save 20 objects. Remove objects to save the change.”

Where can I set that I can insert more than 20 objects there? 

I was in Settings > Issues > Custom fields but i don't find any option to configure it.

It is a Assets objects Type

[Marc -Devoteam-]

Hi @Antonia 

Not this is a non changeable number.

This is set in the UX code of the application.

What is the use case to show 20 objects or more?

[Antonia]

For example, if we change devices and have a change ticket, then we have to document all devices where a change has been made. And we actually use this asset link for this purpose.

[Éric Dagenais]

If you go through the jira system admin page "import external system", you can import more than 20 assets in an asset custom field. I have not tested the limit from there but pretty sure I was able to go up to 40~.

Maybe automation can also bypass.

I don't think that is a recommended usage but having to update some asset custom fields and transfer values from one another, this worked for me.

[JCameron]

Just found this thread after running into this limit while creating some change management automations like what OP described. The intent was to have an ECO intake overview request form with our field team, then once it was approved we'd create the individual work tickets for updating each physical asset. This way both are part of the asset record. 

Unfortunately you cannot bypass this limit using automations, even if you're trying to directly set the field using JSON in the advanced edit section.

My current workaround is to instead use a text field to list the affected assets in the overview, and then have a linked implementation ticket for rollout. Not quite as ideal but "good enough".

[Chris Gray]

Hello,

Just wondering if you found an answer or work around to this issue?  We have the same use case where we need to select all assets affected by a change.  This can be greater than 20 some times.

[Antonia]

Hi @Chris Gray

unfortunately, I have not found any other solution. It is probably firmly anchored in the code.

[JCameron]

You can't even bypass it editing directly with JSON (see my comment above). My current workaround is to instead use a text field to list the affected assets in an "overview intake ticket" (I'm using the built-in "Change" issue type for that), and then have a linked implementation ticket for each affected asset for the rollout once the intake ticket has been approved by our field service team. Not quite as ideal but "good enough" (using the built-in "ECO Implementation" issue type for those). Since those two issue types existed already, I'm guessing they had a similar workflow in mind when they built out this part of the system.

[Antonia]

Set up the Assets objects custom field | Jira Service Management Cloud | Atlassian Support

I found this site and it says "The Assets object custom field can be configured to store up to a maximum of 20 objects."

Maybe somenbody know if one can change the limit??