How to drain time from the main Story when we create Substories?

[Flavien Driard]

In my project, We all plan stories and time allocated during the planning.
But when we start to work, each break down the stories in several substories (to request work from another group for example), but when we do so, the TimeTracker on the main story is rising, and it make the mess with the time planning if the scrum master.

Is there any option to not rectify it manually each time?

[Nic Brough -Adaptavist-]

Ah, you probably don't want to.

The problem here is that Scrum does not expect you to estimate on sub-tasks (an item is either done or not, it can't be partially done), and because there's several different ways to approach the idea of people doing it, Atlassian have avoided the question and not coded for it at all.  If you want to subtract estimates from the parent, you're going to need some code that can do the subtraction or roll-up.

If you put estimates on sub-tasks, some of your reports will work and some won't.  Even if you did something to make them roll up or subtract or whatever, you will end up breaking other reports somewhere.

FWIW, the way around that is to estimate Story-level stuff in Story Points, and use those to do Scrum, and then carry on using estimates for real time estimates (but you'll still need the code for it)