Automation: Is it possible to set the value of triggerIssue custom field in Additional fields

[Boyan Angelov (Nemetschek Bulgaria)]

Hi,

I need to make an Automation rule that runs when issue is created and gets the Parent Link (from Advanced Roadmaps) value, gets the parent issue and takes the value of a custom field from it, then copies it in the same field in the newly created issue. I can get the Parent issue through the Parent link using Branch Rule/related issues fork with JQL like "IssueKey = {{issue.Parent Link}}", but from that point on my current issue is the parent issue and the trigger issue is the newly created one, so in an Edit Issue action I cannot simply set the value of the custom field from the trigger issue, because it copies the value from the child to the parent. Instead I need to use Additional Fields JSON to try to copy the value from the current issue (the parent) to the trigger issue (the child). I use JSON like:

{
"fields": {
"{{triggerIssue.customfield_11100}}":"{{issue.customfield_11100.value}}"
}
}

but when I try to publish it it says "Additional fields contains invalid field(s) in 'update' or 'fields' section: {{triggerIssue.customfield_11100}}".

So it looks like I cannot use triggerIssue on the left side here, or am I doing it wrong?

[Italo Qualisoni [e-Core] · Accepted solution]

In Automation for JIRA Cloud there is a very cool action called "Lookup issues", it allows you to fetch issues using JQL and pass the result into a variable that you can use later as smar value in your rule.

I believe this would solve your issue, you could use this action to fetch the Parent Linked issue using this action instead of using the branch (which I think is the source of your issue here)

Unfortunately this action is not available yet to server , there is an open ticket for this

https://jira.atlassian.com/browse/JIRAAUTOSERVER-53

For now I think you should do this requirement using an app that allow you to do scripts ( such as Scriptrunner or Power Script)

[John Funk]

Hi Boyan,

What is the actual link between the child and the parent? Is it an Epic? Are you using Linked Issues? 

[Boyan Angelov (Nemetschek Bulgaria)]

Hi John,

The link is based on the field "Parent Link", which comes with Advanced Roadmaps (Portfolio) and establishes the hierarchy in the Advanced Roadmaps. Automation for Jira does not regard this field as Parent-Child relation so far, there is a feature request for this which hopefully gets implemented some day. Until then I am trying to find a workaround, but so far I am failing.

Cheers,

Boyan

[John Funk]

what if you manually added another link between the issues using the Linked Issues field? 

[Boyan Angelov (Nemetschek Bulgaria)]

This is what I would like to avoid, as I need the process to be automated. If I go to manually add links between issues, I might as well manually set the field...