Aggregate Story Points to Epic Level not showing points associate with issues that are assigned to t

[Piskorz Magdalena (BD/BTM-IC1)]

Hi Team,

I set up the following automation to aggregate Story Points to Epic Level:

My issue is that: The total of story points calculated on EPIC level should only comprise of story points that are asociated with issues that are assigned to the EPIC: Linked issues and its story points should be not considered.

How to rework my automation to reflect on the epic only Story Points which are linked with this Epic not also Story Point which are associated with thos linked issues?

[Piskorz Magdalena (BD/BTM-IC1)]

Hi @Bill Sheboy ,

thanks a lot for your answer. I cahnge my automation like follow, but it still doest not work corretly:

[Bill Sheboy]

FYI -- Please reply to posts in the same thread rather than starting a new one.  That will help people review this question to know if there are multiple solution approaches.  Thanks!

Your rule should not branch to the child issues, but instead should just use the lookup issues action to gather them to update the total.  And...the JQL for your rule branch was incorrect so would not have worked.

• trigger: value changed for Story Points
• condition: issue type is not Epic
• action: lookup issues with JQL to find the related issues
  • parent = {{triggerIssue.key}} AND status = Closed
• branch: to the Epic parent
  • action: edit issue to update the field from the lookup

For scenarios like this, I encourage you to look at the documentation, the built-in template rules from the rules list, and the library of example rules.  They will help you better understand how rules are constructed, providing examples to follow.

• https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation
• https://www.atlassian.com/software/jira/automation-template-library#/rule-list?systemLabelId=all&page=1&pageSize=20&sortKey=name&sortOrder=ASC

[Piskorz Magdalena (BD/BTM-IC1)]

I set up the following automation and it work as espected. 

What I tested and failed is the following scenario: I created one Epic and 3 child issue under this Epic. Each child issue has 1 story point, so Epic has 3 story points in total. But when I delete one of these three child issues, total story points on Epic remains the same - 3 instead of 2. Wh en deleting an issue and when unsassigning an child issue from the EPIC the automation rule should be triggered again.

And one more question: are there any side effects around automation rule runs on the platform a day…Are there any limitations?

[Bill Sheboy]

When an issue is removed as a child from an Epic, the trigger is different...and so this rule would not trigger.  To handle the case of adding (or removing) child issues from an Epic a new rule is needed.

For example, trigger on a change to the epic link (or parent) field, check if the issue is not an epic, and then use the changelog smart values to update *both* the new epic parent and the previous parent (if there was one).

About your question about automation rule limits, those have recently changed.  Please read this announcement carefully to understand the impact of the changes: https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update

[Piskorz Magdalena (BD/BTM-IC1)]

Hi @Bill Sheboy 

Can you please advise if it looks like this:

[Bill Sheboy]

That would update the current Epic, as with your earlier rule.

Another section would be needed to update the previous epic, where the key is probably {{#changelog.parent}}{{fromString}}{{/}}

And so another rule section would be needed after what you show

• branch: on JQL of
  • key = "{{#changelog.parent}}{{fromString}}{{/}}" AND issueType = Epic
    • action: duplicate of the lookup issues you are showing
    • action: duplicate of the edit issue fields for Story Points Total

[Bill Sheboy]

Hi @Piskorz Magdalena (BD/BTM-IC1) -- Welcome to the Atlassian Community!

Your rule appears to be branching to the incorrect issue, and the lookup issues JQL is incorrect based on what you describe.

Try changing your branch to Epic (parent), and changing the lookup JQL to:

parent = {{issue.key}}

That will return only the child issues of the epic.

Kind regards,
Bill