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
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:
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?
Every team in the world is unique, and so Atlassian believes that each and every team's best way of working needs to be molded to their unique circumstances – ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot