How to include supporting tasks in the calculation of the burnup schedule of Greenhopper?

We are currently using the burnup schedule in Greenhopper in the "Number of Errors" mode. Currently, only standard types of problems (errors, tasks, histories) are taken into account in the calculation of combustion.

Question: Is there an opportunity to consider also subtasks in the calculation of combustion?

Example: Assume we have 3 stories and 8 subtasks associated with them. If I close the story, this will affect the overtaking chart. But if I close the subtask, the chart will not be affected.

I checked the project filter, which also includes subtasks. But for some reason they are not considered on the charts (which is bad for us).

+5
source share
1 answer

At the moment, it is not supported, as you can see in the release. The initial estimate of the time on the quick table is not the sum of the subtask :

We do not plan to change this behavior, because the main purpose of the initial assessment is to calculate the speed. Using sub-task ratings decomposes speed, as discussed in this replies to a message .

In GreenHopper 6.0.3, we included the remaining score, which will be shown as a summary of the sprint footer. See the release notes for more details .

0
source

All Articles