I have many customers that are looking to sum up Story points and other custom number fields from stories to their epics.
Waiting for this feature to be deployed: https://codebarrel.atlassian.net/browse/AUT-476
The current status is "deployed to cloud" - is it available for use on Jira cloud? what's the chosen code for that?
Hi folks - I implemented Carlos' solution and it works like a charm! Thanks Carlos! :)
Having said that, I ran into a couple of scenarios where the Story Point totals get misaligned...
In each of the above cases, the Story Point totals do not get updated on the Epic(s).
So, to address these use cases, I created an additional Automation that gets triggered when a Story is updated. It checks to see if the Epic Link was changed, captures the changed To/From values and recalculates the Story Point totals accordingly.
Here are the Automation settings I used...
I hope this helps!!! ...Cheers! :)
Hi @Didi Goldbart - Yes, that is correct. ...you'll have two separate IF blocks, one for the EpicLinkChangedTo (just as you depicted above), and another for the EpicLinkChangedFrom. Here's a screenshot of the entire Automation Rule...
Also, I ended up adding a 3rd Automation to handle the use case where a child ticket gets Deleted. Here's a screenshot of that Automation Rule as well...
I hope these help. Cheers!
@Guy Anela - This is very helpful, thank you very much (great catch adding the deleted child rule)!
I'm having some issues with the 2nd automation, its seems that an error occurred. I went over the definitions and they seems correct. Do you have any idea how do I inspect those errors? I couldn't find a log or other entry with the error details.
Hi @Elad Ben-Noam ,
Thanks for your message. John from the automation team here.
This new feature has indeed shipped last week. We are just putting a blog together right now to inform customers.
We will also be running through this new feature in a webinar on June 11th: https://www.atlassian.com/webinars/software/how-to-supercharge-your-automation-in-jira-cloud
Below is the smart value you could use. However, keep in mind that at the moment it will only work for summing up subtasks to the parent rather than stories to the Epic.
Hope that helps but any questions, just let me know.
I'm afraid not @Sameer P though if you check out the comments on this post from the engineer who built it, you might find a workaround: https://community.atlassian.com/t5/Automation-articles/How-to-sum-up-logged-hours-using-automation-in-Jira-Cloud/ba-p/1409115
I am just implementing something like this for my client. The original automation outlined by @Carlos Treminio worked perfectly for me!
I added one additional condition though as my client wanted to exclude any issues that are in the "Done" status category. Thought I'd share in case others are interested in the same use case.
In order to achieve this I:
This will monitor the Status of issues and exclude the story points of those issues that are closed.
Epic status by Story Points report in Jira that can also be displayed in Confluence
In the meantime, you can see total number of story points on an epic by following these steps:
Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events