Initiative Parent update also Epic Child. "Parent Link" = {{triggerIssue.Key}}. 1 child to be update

[Mateusz Janus]

Hello Brothers and Sisiters,

I need help again. I need to build automation When Initiative Changed update also child EPIC.

I am using "Parent Link" = {{triggerIssue.Key}} method and it works perfectly fine:

https://support.atlassian.com/automation/kb/automation-for-jira-writing-a-rule-that-copies-a-field-from-a-parent-to-a/

but ONLY in case when I have:

1. One Inititaitve

2. One EPIC

My Scenario is:

1. One Initiative

2. Many EPICS

3. I want to update only one EPIC with customField = YES

The problem is when I add condition ISSE FIELDS CONDITION

Field: customField

Value: YES

between Branch and Action automation rule doesnt recognise this condition. As result when I change Initaitive value still BOTH EPICS are updated instead of One (that One with CustomField=YES)

And i am wondering if such field condition should be set on BRANCH JQL level i.e.

"Parent Link" = {{triggerIssue.Key}} and customField=YES
But this solution doesnt work

[Bill Sheboy · Accepted solution]

Hi @Mateusz Janus 

For a question like this, context is important for the community to help.  Please post the following:

• an image of your complete automation rule in a single image for continuity
• images of any relevant trigger / actions / conditions / branches
• an image of the audit log details showing the rule execution

Until we see those...

I would expect when the condition is added to the JQL for a branch on JQL this would work.  Seeing the complete rule and audit log details will help confirm this.

When you try that JQL with an example Initiative outside of the rule in an issue search, do you find the expected Epic?

Kind regards,
Bill

[John Funk · Accepted solution]

Hi @Mateusz Janus 

Can you please post a screen shot of the rule that you have so far? Also please show details for the branch you are using. 

[John Funk]

Your screenshot is of the audit log and not the rule itself. We need to see the rule. 

[Mateusz Janus]

@John Funk the entire rule is on the left with JQL details

[Mateusz Janus]

[John Funk]

Very good - thanks for that. 

I don't use Data Center very often. Is there an option for the Branch for Children? 

If so, you might use that instead of the JQL. Then add a Condition under the Branch for checking if the field = Yes. 

[Mateusz Janus]

@joh @Bill Sheboy ....my automation with condition works...

It was not about condition itself, there was ANOTHER GLOBAL automation which impacts my second EPIC. Thank you for quick reaction anyway

[Mateusz Janus]

[Mateusz Janus]

sorry but I had to took a photo (screenshoot upload limitation)
ENGI-15292 - INITAITIVE
ENGI-15298 - EPIC 1 (with customfield YES)
ENGI-15299 - EPIC 2 (withOUT customfield YES)

I logs there is full success but log info informs only about EPIC 1

but EPIC 2 is also updated