My goodness Automation has some quirks.
8 hours of head scratching later here is how to sum story points at Epic level after user update.
First, create a Custom Field.
System administration -> Issues -> Custom Field -> Number Field.
I called mine "Story Points Sum for Epic"
Second, create an automation that triggers when a 'Story Point' field is changed.
Step 1
Step 2
Step 3
Step 4
Test the Automation by changing a Story Point somewhere and check log
Thanks Bill, I will look at these suggestions and see if they improve what we are doing.
A new thing: I do need to fix the Story Points Sum for Epic field to be locked. I noticed that the field can be manually overwritten. Of course it corrects as soon as a story points in dependents update.
Paul, we have the same issue with our automation-based cycle time fields. We address that by detecting if any of the calculated fields in the parent are edited manually, we trigger the recalc.
Hi @Paul Cooper and @Bill Sheboy ,
Did you know that JSU Automation Suite for Jira Workflows provides Calculated Fields capabilities on Jira Cloud?
By setting up a simple formula, you can have a field calculated for your Epic based on field values in the stories under your Epic (eg. sum of Story Points). Whenever the value of the field under your stories changes, the calculated field will be updated automatically. Plus, calculated fields are created as read-only fields.
I'm currently looking for Jira Cloud users to join my usability study for Calculated Fields and I'd be happy to schedule a call to get your feedback on our solution. If you would be interested, please DM me on LinkedIn.
Best,
Maria Kazakou
Product Manager at Beecom Products (an Appfire company)
Thanks @Paul Cooper for the write up and @Bill Sheboy for the extra commentary. While this solution works well for Epics that have less than 100 tickets under it, I have a couple of scenarios where we have large epics with +100 tickets and then the calc stops short. Any suggested solution for this?
Hi @Dave Coop
First thing, as this is a very old thread, I recommend creating a new question and perhaps adding a link to this one. That will ensure the maximum number of people see it to offer suggestions.
Back to your question...for an undefined number of issues to sum, that cannot be done with built-in features.
If you knew there would be between 0 and N issues (e.g., 350 issues) your rule could perform this type of summation in chunks. To do this, you could:
Based upon maximum rule length, this approach would work for up to 2000 issues in a single epic.
Also, this would be a very slow rule (if there are many issues), and could lead to service limits problems, shutting down executions of other rules.
Two other approaches are to build your own app / service to perform the sum outside of Jira, and then call that from the rule; or to investigate marketplace apps for calculated fields which are not limited to the 100 issue count.
Kind regards,
Bill
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Jira Administrator
Configure Jira Software, Jira Core, or Jira Service Management, including global settings, permissions, and schemes.
Managing Jira Projects Cloud
Learn to create and configure company-managed projects in Jira Software and partner effectively with Jira Admins.
Learning Path
Become an effective Jira Software Project Admin
This learning path is designed for team leaders who configure Jira Software projects to match a team's processes.