For Server, I cannot get summation of Story Points after branching (Epic (Parent))

[Amed Moreno]

Hello,

I've been researching this and found reference to this article (which is equivalent to a Jira cloud 'Lookup Issues' automation action.

https://confluence.atlassian.com/automation/bulk-handling-of-issues-993924653.html

Seems like it will work this way.  However, as seen in audit log screenshot, when I log action before branching, I get the sum of Story Points: 13.  But then after branching to locate the Epic Parent, I get 0.  How do I get this part to be the original value of 13?

Any help much appreciated!  :) 

Thanks!

[Trudy Claspill]

Hello @Amed Moreno 

The article is discussing how to hand issues in bulk for two different scenarios. It is not directing you to use both options in the same rule to achieve your goal.

In this case you get no value for {{issues.Story Points.sum}} within the branch because entering a branch changes the context for {{issues}}. {{issues}} it looking at the issues list generated by entering the branch, in this case the Epics of the issues that were selected in the Trigger. It is trying to sum up the value of Story Points recorded in Epic issues, not using the sum of Story Points in the issues from the Trigger.

This thread contains an answer for summing story points from stories to their parent epics each time the Story Points on a Story is changed.

https://community.atlassian.com/t5/Automation-questions/How-to-automate-the-sum-of-story-points-for-all-issues-under-the/qaq-p/1607809#M1087

I don't have a link to a working example of using a Schedule trigger to do this in Jira Server/DC, and I work in Jira Cloud so I don't have access to a system where I can work out the solution.

In an answer on this post, @Bill Sheboy hypothesized that it could be done be selecting Epics in the schedule trigger and then using the branch to drill down to the child issues for each Epic to get the some of the child issues. Unfortunately there is not a working example of that in that post.