Automation with custom field from a linked issue

[Crystal Wang]

Hi,

I'm having trouble with an automation. I'm trying to copy the values from a custom field that is a multi-select option list (like Labels) of a Parent to the triggering issue.

Trigger: Parent Link (Match) value changes (in this case Parent link is used for the hierarchy above Epics, not subtask to task)

If: Parent Link is not empty

Then: Lookup issues: key = {{issue.Parent Link}}

And: Advanced edit

{
  "update": {
    "[Custom Field]": [
      {{#lookupIssues.[Custom Field]}}
        { "add": "{{.}}" }{{^last}}, {{/}}
      {{/}}
    ]
  }
}

I'm getting the error:

"com.codebarrel.automation.rule.error.action.additional.field.update.operations.invalid.execution

[Custom Field]"

It works fine taking [Custom Field] from the current issue (I tested by changing the beginning to "labels": [{{#issue.[Custom Field]]....)
I believe lookupIssues is working since I can get e.g. #lookupIssues.summary to copy over but not labels or my Custom Field.

[Bill Sheboy]

Hi @Crystal Wang -- Welcome to the Atlassian Community!

Are you using Jira Server or Data Center version of automation rules?

If so, the Lookup Issues action does not support most fields yet, including custom fields.  Here is the suggestion to add those: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877

The workarounds depend upon what you are trying to do, and I suspect you will need to call the REST API issue search (with the JQL from the lookup) using the Send Web Request action.  Please see this post for more details: https://community.atlassian.com/forums/Jira-articles/How-Can-I-Sum-Up-Multiple-Issues-into-a-Parent-Number-Field/ba-p/2882712#M16701

Kind regards,
Bill

[Crystal Wang]

Hi Bill,

Thanks so much for the quick response! I'm not quite sure which version we're on, but I know we're not on Jira Cloud yet (I believe we'll be moving over in a couple months). I also don't have the permissions to create an API Token in my organization so I will see if someone else can try to do the REST API workaround or I'll just revisit this when we move over the Jira Cloud.

Thanks again,
Crystal