Hello,
I was able to make automatization for sum up of Story point estimate of tasks to Epics. Now I have a problem that I need to sum all tasks in epic, that are in state of : "draft, ready, in progress, review", thus everything that is not in state of "done, won't do". What would be the best options?
The first rule was made thanks to this thread: https://community.atlassian.com/t5/Jira-Software-questions/Sum-up-story-points-in-epic/qaq-p/2258306 which works well.
Thank you!
Hello @Ondřej Rolník
The rest of the automation is extended on the same flow. Three lookup issues with minor changes gives os total points, completed and remaining in a single automation.
Please see the automation below which covers all three points I've mentioned in the answer above:
@Sanjog Sigdel Thanks, but now is Jira not able to write numbers to the Total Story points left/completed. This is code I have put in the "Edit issue field" of Story points done: {{lookupIssues.Story points estimate.sum|0}} - what do you have there?
When I look in the log, it says that Epic is not meeting the conditions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have {{lookupIssues.Story Points.sum}} for all three fields. The jql in each lookup issues separates tickets with completed, remaining and total story points. This smart value sums the story points.
This is how it works for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sanjog Sigdel Yes, I have made it that it works, thank you very much. The last problem is the condition of "won't do". What should be the syntax? This does not work for me: "Epic Link" = {{issue.key}} and Status = Done and Status = Won't do.
I need it to count the SP of both 'done and won't do' tasks to the Total Story points Completed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Ondřej Rolník
It should be like
"Epic Link" = {{issue.key}} and Status = Done AND Status in (Done, "Won't Do")
For a good practice to eliminate errors, better if you replace Won't Do to Wont Do. Just to be in safe side such that the single quote ' won't create any issue.
Please validate your JQL first from the Jira Issue Navigator then you can add it in the lookup issue query.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sanjog Sigdel Yes, finally it works, thank you very much!
One last idea, do you think that there could be a possibility to make this automatization "live on its own"? Because as I see it, there is a slight problem with the trigger (mine is When the field "Story point estimate" changes). It would be better if Jira could read the task story points all the time, because it does not read when task moves from for example "processing" state to "done" state, thus the epic SP count does not change. It would need the change in SP all the time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have propably found better solution ->the trigger should be "When the issue is updated" and it seems to work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Ondřej Rolník
I am running Jira Standard Plan so my Automation rule limit is 500. But if you have premium Jira Plan, you can run as many automatio nrule as you want. In that case the trigger can be whenever the Story Point value gets changes.
Better than the issue is updated, keep it as whenever the story points value changes, check the rule automatically.
Kindly accept this solution for future reference. Glad it worked for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Ondřej Rolník
It must be your lucky day today. I had the same curiosity few months back and I got it resolved via Jira Automation.
My requirements is similar to yours. In addition to that I've implemented the following:
This is implemented via Jira Automation and Lookup issues.
Link to the community question:-
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, @Sanjog Sigdel thank you, but there is no guide on the link you posted, there is just a guide for total points, not for the SP completed/remaining.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"I was able to make automatization for sum up of Story point estimate of tasks to Epics. "
Could you share that automation with me? I have been trying to do the same thing and unable to get it to work properly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.