Cloning a ticket does not copy linked asset

[Jeroen Gouma]

We have a monitoring application which creates tickes in Jira Servicedesk via API call. 1 of the fiels populated is the asset from the Jira Assets. This works fine.

However, each Servicedesk is cloned into another project for a specific team. This works fine except for the link to the asset. This means the consultant can not click to the asset involved. Issue types and forms are the same on both sides.

Customfield_10681 is the field holding the asset-id.

Tried a lot of things, but I think I overlook some small thing :-(

Any help would be appreciated!

[Paul Ceronio]

@Jeroen Gouma ,

Hi Jeroen,

I am facing the exact same issue of trying to copy the the linked asset to the cloned issue in another project. Did you solve this in the meantime? Could you share how, please?

Best regards

Paul

[Jeroen Gouma]

Hi Paul,

we did not manage to solve this. This, and some other issue's, forced us to redesign the implementation.

All monitoring events now go directly to the correct project (makes sense at the end).

So sorry, no solutions on hand.

Kind regadrs,

Jeroen

[Paul Ceronio]

Hi Jeroen,

Thanks very much for your reply.

For my requirements, I just managed to implement the automation recommended in this support article:

https://support.atlassian.com/automation/kb/how-to-copy-assets-fields-when-closing-issues-by-using-automation-for-jira/

(Even then, it took some time reformatting of the JSON before it would work... :))

The cloning rule now looks like this:

The JSON code:

{
"fields": {"customfield_10400": {{issue.customfield_10400.asJsonObjectArray("key")}}
}
}

(Replace "customfield_10400" by the respective Assets field identifier in your instance.)

Not sure this is exactly what you were looking for, but I'm partially posting this here for anyone who might want to take a look and for my own documentation of course.

Kind regards,

Paul