Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Velocity chart doesn't show data in hour estimation

Hi everyone!

My Velocity Chart doesn't show any information about my sprints.

I like to use only hours to estimate my stories and subtasks.

My board has this configuration (below):

My burndown chart works perfectly.

But my Velocity chart don't.

I was expecting that it showed my sprints' velocity in hours. But it doesn't show nothing.

Can anyone help me ?



4 answers

Frederico, it's been a while since you posted this, so you probably found the issue or are not interested anymore. Anyway, I think the problem you have (same I have) is that you are using sub-tasks. 


I think JIRA calculates Velocity using the time (only) from the story, but not aggregating time estimates from sub-tasks. There is a big discussion around JIRA community on when Atlassian will start calculating story time estimates adding the sub-tasks estimates:


Hope this helps to everyone stuck with the same problem. 

Very weird because I have completed a lot of issues in each sprint.

This is my collumn configuration :

This is a completed story from a past sprint. We can see the logged hours and other informations.

I still dont understand why it doesn't show like yours.

Some idea or tip configuration to check?


Not sure, but you can check the sprint report to see what was calculated for inclusion and then see what issues you had.


On Sprint Report, it shows "Original Time Estimate (0)"

But I dont know why it's showing zero hour(s).

I will tell you how I create/start my sprints:

1) We create a lots of story issues

2) We select some stories to sprint

3) We create a new sprint and set some stories into it

4) We create sub-tasks into each story and for each sub-task we set a estimated work in hours.

5) We have all stories planned with their sub-tasks and these sub-tasks have working remaing planned in hours.

6) We start the sprint.

So... that's it...

I did this since the beginning and I have never had problems... only with this Velocity chart.

Am I doing something wrong?



Are you setting estimates at the story level or only on the subtasks? The velocity chart does not consider subtasks.

so that's it :(

I only set hours for the sub-tasks... and then I consider that the story estimative is the sum of all sub-tasks...

But... Is this wrong ?

No its not wrong, we do a similar thing per team. If only there was a few settings on these charts and we'd all be happier.

The Velocity chart will show hours, but the catch is that it only shows hours for completed issues. So, if you've completed 90 out of 100 hours for an issue it will show as 0 for completion. Additionally, completion is based on the statuses that you've mapped to the Done column in the sprint configuration.

Does anyone know a way to get a Version of this report that shows actual hours completed (including hours burned down on issues that were not completed) I realize this is not "pure scrum" but it is the way my team likes to measure work completed in a task. We can't be the only ones - is there a plug in out there already?

Velocity chart will not be based on hour. Velocity chart shows how much work was commited and completed at the end of the sprint. Storypoint is most common measure of the amount of work completed in agile.

You can always estimate each stories in story point before the start of the sprint and continue taime tracking in hours during sprint. This will allow you to see a burndown in hours and velocity in story points.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

2,606 views 6 23
Read article

Atlassian Community Events