Time Estimate always shows 0 minutes in the Version widget of the Planning Board

Hi

I create several tasks of a story, and assign all of them to my first sprint Sprint-1 (the Version), i set the original estimated time for each tasks to some value, so i assume the Time Estimate in the version widget (for Spring-1) should have a value that is the sum of each task's original estimated time, but it always shows "0 minute", did i miss something? Thanks

Cheers
Ramon

7 answers

1 accepted

The issue is still not resolved, one thing i'm sure is that it must have something to do with the sprint start date, if i set a newer start date i can get some estimate value. Any ideas? Thanks.

Do you have a start date for the sprint?

Yes, I do set the start date for the sprint.

I am having the same problem. I also have a start date set for the sprint. When I view hours burn down charts it shows the time estimated but not in the vesrion widget on the planning board.

Any ideas on what I need to do to resolve this?

I am having the same problem. I also have a start date set for the sprint. When I view hours burn down charts it shows the time estimated but not in the vesrion widget on the planning board.

Any ideas on what I need to do to resolve this?

I am seeing the same thing. If I change the sprint start to to some time after the estimates were entered then they show up.

Could use an explanation on why this is if anyone knows...

I think I found a work around, you need to create story+task first and assign them the right estimated working days, after that, create your new Sprint (version, better start from today), then assign your stories and tasks to this new Sprint, you should see the estimated working days displayed correctly in the version widget. For my 2nd sprint, i can see the correct estimated working days.

I think it's still a bug, but it's enough for me to have a work around.

I put in a support request with Atlassian and found that this is working as they have designed as follows:

  • The "Time Estimate" field shows hours for issues that were planned. That means issues that were created and estimated before the start of the sprint.

  • All other issues, the ones that are created in between the dates of start and ending of the sprint, will be counted on remaning work, "Time Remaining".

Hi,

I use JIRA 4.2 with Greenhopper. The issue is, Time Estimate field is not showing the correct planned hours for my sprint.

I created few subtasks after sprint start date and my Time Estimate field is showing some hours and it is not showing the exact planned effort. Is it mandatory to create stories and subtasks before a sprint's start date.

Due to this, my Hour burndown Chart does not plot the graph as expected. The graph does not show the correct Estimated hours in GuideLine value.

Any help to resolve this?

Regards,

Balu

I was having the same issue, the point was that I was, just filling original estimate, and forgot remaining time, then JIRA automatically sets remaining time to 0!

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Jira Software

How large do you think Jira Software can grow?

Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...

280 views 4 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you