In an automation triggered by Issue created, can I update a custom field in the parent issue?

[Phil Bustin]

In an automation triggered by Issue created, I tried adding For: Parent branch to set a "Global ID" custom field to {{issue.key}}.  The branch seems not to be in the log at all.

Before I tried this, I tried to find a trigger for a separate automation for the Epic when a child is created, but I couldn't identify such a trigger.

Issue created automation

More of the automation

Automation log

Note that the Edit issue in the log seems not to be from the For: Parent branch, but the next edit that is further down.  The displayed issue key (the Story key) seems to support this.

[Mark Segall · Accepted solution]

Hi @Phil Bustin - The "For Parent" branch is intended for Sub-Task issue types.  If this is not a sub-task, it will have no parent.  Instead you would want Epic (Parent)

[Phil Bustin]

Wow!  That worked!  I guess I stopped at "Parent" without going further down the list.

Now I have another problem--I guess on account of timing, the Story Create transition post action didn't pick up the parent's custom field value.  That post action works in a different setting--when a JSM issue clone creates the Story.  For the Epic > Story setting, I'll have to try to set the field in the same automation that just succeeded in setting the custom field in the Epic.  I'll post with the result around 1 pm Eastern time.

[Phil Bustin]

The Copy field action in the Story also works.  Similar to the selection of Epic (Parent) in the Epic field action, I had to select "Copy from Epic issue" in the Story field action.

[Laurie Sciutti]

Hi @Phil Bustin ~ you'll want to add it via the "More options" section...sample shown below.

[Phil Bustin]

Thanks.  Using the smart value worked instead.