I am getting Velocity chart commitment and Complted as Zero.

kishore nimma July 15, 2019

Hi Every one.

we are estimating and log hours with subtasks and when we are working on issues it was showing orginal estimation and remaining and logged time in parent with subtasks.

But not in the velocity chart

Is there any possibility to include sub tasks estimation and logged time in Velocity chart.

We are unable to get sub task estimation in velocity chart. It is showing as Zero.

1 answer

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 17, 2019

hello Kishore, 

In fact, it is expected that JIRA does not take into account the estimate from Sub-tasks in JIRA Reports. In this thread, you can see a clear explanation of why we have not configured JIRA to work with sub-task estimations:

Why not estimate on sub-tasks and roll that up for Velocity and Commitment?

Many teams break down stories in to sub tasks shortly before the sprint begins so they can use the stories for tracking. This raises the possibility of using the sum of the estimates on the sub-tasks as a way to decide which issues to commit to in the sprint (and potentially for velocity).

As described above, tracking is really a separate process from estimation and velocity. The estimates that are applied to the sub tasks are clearly higher accuracy than those that were originally applied to the story. Using them for velocity would cause the velocity to have both high and low accuracy estimates, making it unusable for looking further out in the backlog where stories have only low accuracy estimates. In addition, only items near the top of the backlog are likely to have been broken to tasks, so using task estimates for velocity means that the velocity value could only ever predict the time to complete the backlog up to the last story that has been broken in to sub-tasks.

Using the sub task rollup to decide the sprint commitment would also be dangerous because unlike the velocity value it does not take in to account the overhead of unplanned work or interruptions.

We have created a feature request to add the option to sum sub-task estimation to Stories, allow their management in JIRA Reports:

Sum estimates from sub-tasks in user stories

That been said, some third-party partners have developed apps that can provide the user with this functionality. Here are some options that give you this feature:

AIM Agile Planning for Jira

Plangle for Jira Software

Additionally, feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates. Also, check all the other workarounds and plugins provided by other users in the same Feature request.

Let me know if you have any questions about the proposed options.

Suggest an answer

Log in or Sign up to answer