Story Point Summation of Sub-Tasks, But Not Including Resolution of Done

[Andrew Zebroski]

Hello!  I'm hoping for some assistance around the topic of summing up story points at the sub-task level and having that total shown at the Task level.  However, I do not want that total to include story points for sub-tasks where the Resolution has been updated to Done.  I've been reading numerous other posts and comments, but they are all a bit more complex as they go down the path of scrum theory, burndown, linking stories, etc.  Our situation is much simpler based on our use case and introducing some JIRA basics to our user group.  We're not exactly following Agile/Scrum methodology to the T.

Screenshot below is what I have setup right now with the JIRA Automation, but what I have gathered is that if I change a sub-task status to Complete, the Automation just doesn't apply to that change, and the Story Points are left alone versus subtracting from the Total.  Meaning, the Story Points at the Task level are remaining static.

Use case we are looking for below:

Story Points for Sub-task 1 = 3.  Status is In Progress

Story Points for Sub-task 2 = 3.  Status is In Progress

Story Point Total for the Task = 6

Sub-task 1 moves to a Completed or even a Cancelled status

Story Point Total for the Task needs to then equal 3

Here is my Automation screenshot:

Can someone please assist?  I'm not a technical person AT ALL, but I would imagine there is an easy way to do this that makes sense to a non-technical person....

[Nic Brough -Adaptavist-]

Do not do this, it will break all your reporting.

Sub-tasks are a fragment of a story, and not sprint items, so Jira ignores them in estimate reporting.  Strictly speaking, estimates on sub-tasks are nonsense, but if you want to do it, you need to think through the mechanics.  (I don't think there's anything wrong with doing it myself, but Atlassian have done the minimum in Jira - not defined anything that can handle it)

If you must put story points on to sub-tasks, then use a different field for them and automate the sum from sub-tasks to go into the different field.  For example:

• Field on sub-tasks called "Sub Story Points"
• Field on issues called "Story Points"
• An automation to handle rolling up the values in Sub Story Points that puts the result into an issues Story Points alongside the issue's own Story Point estimate
• Scrum estimation set to Story Points

[Bill Sheboy]

Hi @Andrew Zebroski 

You appear to be using Jira Server, which does not have Lookup Issues in rules yet, and so your other option is smart value list filtering (which I believe works with Server rules based on other posts).

Kind regards,
Bill

[Kristján Geir Mathiesen]

Hi @Andrew Zebroski and...

Maybe you should change your trigger from "When value changes for Story points" to when status changes. That could be a better trigger.

HTH,
KGM

[Andrew Zebroski]

Hello, and thank you!!  I think I'm understanding the concept, but I'm probably not updating the automation correctly.  I tried the below, and the story points are not updating to reflect that status change.  That is, they are not subtracting if the sub-task is updated to Completed.  Here is what I tried:

And other attempt:

[Kristján Geir Mathiesen]

Hi again @Andrew Zebroski 

I haven't done this before. Maybe you should try:

{{issue.Story Points.plus(issue.subtasks.size)}}

You can read more about Smartvalues math.

HTH,
KGM

[Andrew Zebroski]

Thank you for the resource...I'll take a look!  Can't quite the right solution, but I know its out there!