You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I feel like I'm very close with this automation, but still haven't been able to quite figure it out. I'm wanting to track the total story point estimates of all issues in a "To Do" status that pertain to the same story by having that total number in a field of the story.
With this automation I've created below, I'm able to sum all the story point estimates of my issues in the "To Do" status, however, when the status changes to "Done", the sum doesn't change.
I'm wanting to track the total amount of story point estimates we have left for a project in a way that when an issue is marked as "Done" its story point estimates won't be included with the total left to do in order to finish the project as a whole. This is what I've put together so far,
Below is each automation section mentioned above expanded
With this automation in place, it calculates the total story points I have in the To Do status and inputs that total to the linked story of the issues as shown below in the Child Story Points Left TO DO.
Once I change one of those issues to a "Done" status, the total still shows as 20. I want that total to adjust and not count the issue that is now Done.
Any help to this would be great! If I need to change this automation or if I need to create another automation as well that will do the subtraction that would work too. Any and all help would be appreciated.
Hi @cjohns -- Welcome to the Atlassian Community!
If I understand your use case, for any linked issues, you want to sum the remaining (non-done) story points into a custom field...regardless of the issue type hierarchy. And, this means that the same story points could be summed in multiple different issues (due to bidirectional linking). Please let me know if I am misunderstanding your use case.
The condition in your rule which checks status = To Do is halting further processing. There are a couple of ways to solve this:
I recommend #1 as you are more likely to have accurate results, easier testing, and easier maintenance for future changes.
Thanks for your response. If I'm understanding your clarification correctly, I do want to keep the issue type hierarchy meaning that if I have four issues that all together total 20 story point estimates and those same four issues are linked to Story 1, then Story 1 should show "20" under the custom field.
I am new to Jira and have been reading a lot on automation and how to understand it more, but I don't quite know how I would put what you are saying into practice. It makes sense what you are saying, but I don't know how to translate that to the automation.
This is what I put together, but I'm missing something to have it only sum up "To Do" tasks and remove the task if it is changed to a "Done" status.
I'm not completely sure what I need to add or change from this to sum it up to the linked story.
Thanks again for all your help!
Thanks for that information, @cjohns
I am still unclear what problem you would be solving with this use case, as there could be an interlocking tree of linked issues, and so that summed story points field may not be meaningful. It may be safer to only sum values for a parent issue to children, and I suggest considering that approach and discussing with your site admin before proceeding.
One TODO: please consider what to do with this custom field when an issue completes/moves to done: should it stop updating or continue to update or be cleared. After you decide that you may update the rule(s).
You will also need a rule triggered on changes to issue links, so I recommend three rules to reduce the amount of duplication:
Such a rule #3 would be close to what you have done:
Please note: this will be a slow rule to process and could in fact fail if multiple issues update in a short window of time. For example, at the end of a sprint or rapidly moving things on the board.