You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
So we have Agile stories. We then as the Dev and QA to create tasks on each of them and estimate them. Want to estimate them by hrs burned down as the task is pushed to Done. We have a prod ready stage where the story goes to before we push it to DONE; which happens after the deploy.
Expected: As tasks get done and their hrs completed the burndown must go down.
It is not going down as such.
Comments: It does go down when the stories are removed and added but not when the tasks are getting pushed to Done.
Hi @Roger Pras,
Stop struggling with the limited Jira reports. Our Great Gadgets app offers all you need for tracking your agile projects in an easy and efficient manner: Sprint Burndown Chart, Release Burdown Chart and Team Velocity Chart gadgets that support any type of estimate (including time estimates) and can include the sub-tasks in the calculation.
For how to use these gadgets with time estimates, see this article from our blog:
This app offers many other gadgets that you will find useful. It can be a great asset for your team or company.
I hope this helps. If you have any questions, please contact us at email@example.com.
Hello @Roger Pras
Welcome to the Atlassian community.
Can you show us an example of a Story where you have created a task? Are you actually creating child subtasks, or are you creating stand-alone Task issues and linking them to the Story?
I have been using Jira for more than 10 years and have done this before. Just not sure what is the issue this time.
Yes we have stories and then subtasks usually like a Dev task for say 4 h and a Qa task for 3 h. So total 7 h. When that story is pushed to Prod deploy status (and not Done) I expect that the total of say 240 hrs for the sprint now show 233 on the chart meaning ot must go down 7 hr. But it does not. I can trace the remaining time estimate on tasks and notice each task gets to Done it must be reflected. But is there a mistake in my setup where the Jira is setup to measure against the stories so even though the task is getting Done ( the story is not done) it is not reflecting that?
Appreciate your answer. There is no way I can copy and past the chart in here?
Are you working with a Company Managed project or a Team Managed project?
Are you working with a Scrum board or a Kanban board?
Which burdown report are you reviewing?
Which column are the subtasks and parent story in on your board - all in the column farthest to the right, not the column farthest to the right?
Do I understand correctly that you are moving the subtasks to a status that is in the column farthest to the right, but the parent issue is not getting moved to that column?
And in that case the burndown chart does not reflect a decrease in the hours equal to the time in the subtasks?
But if you move the subtasks and the parent issue to the column farthest to the right then the burndown chart does reflect a decrease in the hours?
What is the Estimation Statistic for your board?
What is the metric you are displaying in your burndown chart?
Do you have Remaining Estimate and Time Spent enabled in Estimation for your board?
This article on the Burndown Chart talks about how the burndown works with respect to subtasks vs. their parent issues.
So answering your questions.
1. The subtasks have the hours and when they are moved all the way to the right column then the hrs do not get reflected in the chart.
2. Not measuring on the story level.
3. Using Remaining Time estimate as the metric and that is what is on the vertical axis.
Somewhere the settings are messed up whereby the subtasks' hrs are set to complete as example estimated 4 hrs. Task completed and now the remaining estimate = 0 h. That must show for the sprint that if 240 hrs...it is now 236 hrs. But this is not reflected.
Is it possible that The setting is not configured to count the sub tasks hrs? That is why it is not reflecting. Also our stages are from left to right:
To Do. (left. first sage)
Done (furthest Right)
Our stories sit in Prod Ready status when the tasks are all completed. Done is only done at end of sprint when the deploy happens.
Is this a bug on the part of Atlassian? or is there a setting that needs to be adjusted. It is clear that the burndown reflects the changes when stories are added and when removed. This is what the current graph is displaying.
However I want to track the hrs burned for the tasks. There does not seem to be a way to include that in the burndown chart. Need to see that each time the task is done the red line goes down and the green line goes up to a point that thy intersect somewhere in between on the graph. This is not happening and not seeing any option to include tasks as the "grain" for this measurement. Have seen this before. Not sure if there is some setting needed . If I am able to select the burndown "grain" as tasks this should work fine.
I am not sure that I am clear on the Estimation settings for your board.
Can you provide a screen image of the Estimation setting page for your board? Like this:
Note I'm not asking you to change your settings. I want to see what your current settings are.
I ask because Remaining Estimate is not an option I see in this screen for the Estimation Statistic field.
With these settings, and with the Burndown Chart statistic set to Remaining Time Estimate, when I log work against either a subtask or its parent issue and reduce its Remaining Time Estimate, the change is reflected in the Burndown chart regardless of the status of the subtask or its parent task.
In the following two images I first used Log Work to log time and reduce the remaining estimate on a subtask, and then on its parent issue.
The status of the subtask is "To Do" and status of the parent is "In Progress". Neither status is mapped to the column farthest to the right on my board.
If you have Remaining Time Estimate as the Y axis of this change then it should be reflecting changes the the Remaining Time Estimate of both subtasks and parent issues in the sprint as the Remaining Time Estimate is reduced by using the Log Work option.
Can you provide screen images that show your board settings, chart, and time logging activity against issues to illustrate your problem?