Automation branch rule / related issues not working for parent link

[Daniel Starkey]

Hi,

In Jira we have the following configurations/hierarchy for our issue types;

- SAFe Epic                  (Custom issue type)
       - SAFe Feature      (Reused built in Jira Epic - links to SAFe Epic on Parent Link)
            - Story               (Standard Jira Story - links to SAFe Feature on Epic Link. This is                                          where we capture Story Points)

Using Jira Automation, we'd like to be able to aggregate the number of story points and store them against the parent SAFe Feature. Then aggregate them and store them against the SAFe Epic.

I've created a Global Rule as a proof-of-concept, that is supposed to send an email of the linked SAFe Epic's Summary field (to prove that we can access the SAFe Epic from Automation when a SAFe Feature is updated). It is triggered each time the Story Points field on the SAFe Feature is modified. I then try finding the SAFe Epic based on the Parent (link) using the branch rule / related issues. But, it never enters into the Send Email action.

[Daniel Starkey · Accepted solution]

I've managed to get it working by using a JQL query to work out the related SAFe Epic (custom issue type) based on the Parent Link field

[Bill Sheboy]

Hi @Daniel Starkey 

Given the way your solution rule's trigger is written (all issue story point changes), please consider the number of executions of that global rule and the limits:

https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/

Best regards,

Bill

[Hana Kučerová]

Hi @Daniel Starkey

welcome to the Atlassian Community!

To be able to get Epic (SAFe Feature) issue to your stories, please try to change the "Branch rule / related issues" from Parent to Epic (parent).

Then I think you need to create the second rule, which will react to change of Story points in SAFe Feature. There you will need to use "Branch rule / related issues": Linked issues. You should allow rule trigger for this one, because it will react to the first rule's updates.

[Daniel Starkey]

Hi @Hana Kučerová 

Thank you for your response!

I've managed to get the first part working so the user story updates the Jira Epic (SAFe Feature).

I'm unable to get the second part working. The automation is triggered by the Epic (SAFe Feature) being updated, but it doesn't enter into the Branch rule / related issues section when using the linked issues either.

Thanks,

Dan