Sum up story points of all issues linked to an Epic

christopher.branaman

I have seen several posts about this issue but I still haven't been able to get it to work. 

We're on JIRA Cloud

Company Managed Project

I tried 2 different solutions, neither of which worked.

Here is the first  (didn't have room to capture the entire screen but the first steps is the one at the right "Field Value Changed")

Here is the second one I tried

In the story points field I used 

{{lookupissues.Story Points.sum}}

Any help would be greatly appreciated.

Trudy P Claspill

Hello @christopher.branaman 

@Jehan Bhathena provided information about a version of a rule that could work for you. I want to address why what you have did not work.

 

To really explain why they didn't work though, I need to know in what way exactly do each of these not work? Without that information I can point out some possible problems.

 

In the first one you have two Lookup Issues actions; one based on something you called "Epic Key" and one based on "Epic Link". What is the one based on "Epic Key" supposed to be doing? Do you have a custom field named "Epic Key"?

Also be advised that the second Lookup Issues action overwrites the results of the first one. If you actually need to retrieve two sets of issues and combine the results; with one issue set based on Epic Link and the other based on Epic Key, those selections need to be combined in one JQL in one Lookup Issues action.

 

In the second rule the Lookup within the branch is wrong. You can't use the Epic Name from the Epic as the value when searching on the Epic Link field for child issues. You would need to use

"Epic Link" = {{issue.key}}

 

Additionally, Atlassian is deprecated the "Epic Link" field and replacing it with the "Parent" field. In many systems they have already disabled the ability to use the "Epic Link" field in screens and filters, or provide warning messages when the "Epic Link" field is used. This may not yet be true in your instance, but you may want to check on that.