How to copy Assets (Insight) field value to another issue via Automation for Jira?

[Венера]

Hello!

I have two projects. When an issue is created in Project A, a linked issue is automatically created in Project B. I need to copy field values from the first issue to the second.

Problem: All standard fields copy correctly, but the Assets field does not transfer.

Details:

1. The Assets field has the same ID (customfield_13602) in both projects.
2. The field is added to the Create and Edit screens in both projects.
3. Both fields reference the same Assets schema and object type.

What I've tried:

1. Standard copy via Automation UI (doesn't work for Assets fields).
2. Editing the issue after creation using JSON:

   {
   "fields": {
   "customfield_13602": {
   "key": "{{triggerIssue.customfield_13602.objectKey}}"
   }
   }
   }

   1. Setting the field directly during "Create Issue" action.
   2. Using "Lookup Objects" action to find the object before writing.
   3. Attempting to use AQL queries — but discovered that it's impossible to use AQL in automation for Assets fields, as mentioned in Atlassian documentation
   Nothing works. The field remains empty, and there are no errors in the audit log.
   Question: How do I correctly pass an Assets field value from one issue to another via Automation?

[Marc -Devoteam-]

Hi @Венера 

Welcome to the community.

Before creating the new issue, store the value to the assets field of the trigger issue in a variable, make sure the variable get the key of the assets object.

example for creating variable: {{issue.customfield_12345.Key}}

In the create action, set the asset field with smartvalue Key = {{variable_name}}

[Arkadiusz Wroblewski]

@Marc -Devoteam- 

I agree. Even in Cloud, it’s often a good idea to first store the Value after fetching it and then use it in the post function.

[Trudy Claspill]

Hello @Венера 

Welcome to the Atlassian community.

Referencing this KB:

How to copy Assets fields when closing issues by using Automation for Jira 

If it is a single value field then you should be able to set the Assets Object field during the Create Issue action using JSON code;

{
  "fields": { 
    "customfield_13602": {  
      {triggerIssue.customfield_13602.asJsonObjectArray("key")} 
    } 
  } 
}

I don't have a Jira/JSM Data Center where I can test this to confirm it works.

[Arkadiusz Wroblewski]

Hello and welcome @Венера 

I have a pretty similar use case, but I solved it a bit differently.
If you are really cloning the issue, and not creating a brand new one from scratch, then I would first try the native clone options in Automation. During the Clone issue action, you can already copy field values from the original issue at the same time, and in cases like this that is often much simpler than trying to set the Assets field afterwards. You must make sure this field are active in another project.

So for me, the first question would be: are you truly doing a clone, or is it more a create new issue based on another one use case?
If it is a real clone, I would definitely test the built-in field-copy behavior first, because that should normally work much better than adding extra update logic afterwards.

[Венера]

Hi, thank you for your suggestion!

To clarify: I am **not using the "Clone issue" action**. My workflow uses the **"Create issue"** action to generate a brand new issue in Project B based on the trigger from Project A.

So the process is:
1. Trigger: Issue created in Project A
2. Action: **Create new issue** in Project B (not a clone)
3. Goal: Copy field values from `{{triggerIssue}}` to the newly created issue

Since it's a fresh creation (not a clone), the native clone options don't apply here. I need to map the Assets field value explicitly during or after the "Create issue" action.

[Arkadiusz Wroblewski]

@Венера 

if you are using Create issue and not Clone issue, then I would not expect the native clone behavior to help here.

In that setup, Automation is creating a completely new issue in Project B and trying to carry over the Assets value from {{triggerIssue}}. That is a different scenario than standard clone-based field copying.

Since your standard fields are copying correctly, but the Assets field stays empty without any audit log error, that points more to how Automation is handling that specific field during issue creation. It looks less like a screen or field ID problem and more like an Assets population/linking problem.

In JSM Data Center, that usually needs a different approach. Simple field mapping during Create issue often is not enough for Assets fields. In many cases, the more reliable way is to:

create the issue first

then update/link the Assets field explicitly usually via REST API or Send web request.

So yep, I would stop focusing too much on screens here.

The more likely root cause is how the Assets value is being written, and the practical next step is usually to move to an API-based update after issue creation for that field.