Is there a way to refresh story points on subtasks that move parent tickets?

Question

I have story points on subtasks that automatically refresh totally up to the parent ticket.

If I move a subtask, the story points do not deduct from the old parent and do not update the new parent ticket's story points. Is there a way to automatically refresh the story points?

Background: We are trying to count story points for bugs in each sprint. We want a task to have 40 story points a sprint. Every time a new bug is raised, we want to move the subtask to a new bug and count the points on that bug. This way, the story points should deduct from the tasks and we are not adding more story points to the sprint.

Example:

Original Story Points Summed Up from Subtasks:

* Parent #1 = 3 story points* Subtask 1- 1 story point
* Subtask 2- 1 story point
* Subtask 3- 1 story point

* Parent #2 = 0 story points (no subtask)

----- Move subtask (More --> Move --> update new parent ticket #)

Actual Result:

* Parent #1 = 3 story points* Subtask 1- 1 story point
* Subtask 2- 1 story point (moved the Parent #2)
* Subtask 3- 1 story point

* Parent #2 = 0 story points (no subtask)* Subtask 2- 1 story point

Expected Result:

* Parent #1 = 2 story points* Subtask 1- 1 story point
* Subtask 2- 1 story point (moved the Parent #2)
* Subtask 3- 1 story point

* Parent #2 = 1 story point (no subtask)* Subtask 2- 1 story point

Ryando_poco · Answer

Hi @Oksana Baier I have a slightly different issue compared to yours. Mine could refresh the old parent, but the new parent cannot be restored to the new calculation.

For refreshing the old parent, you can create the automation like this below picture.

If you don't mind, could you share how I can refresh story point in the new parent?

Warm Regards,
Ryan

Bill Sheboy · Answer

Hi @Oksana Baier

There are several ways to do that...and one way is to:

* Create a rule, triggered on some condition, which updates an story to recalculate the sum
* trigger that condition

For example, you could detect the parent change for the subtask and then update the parent.  The trigger for this approach would be Issue Updated followed by an Advanced Compare Condition to detect the parent changed for a subtask issue type.

Kind regards,
Bill

Oksana Baier · Answer

I have the same automation for summ of original estimation for epic and story from child tasks. But I cannot understand how I can refreash old parent after movement subtask from one story to next. I write automatization for refresh new parent, but dont know how to refresh old parent, please help me :)