We currently use stories where there is only one resource working an effort or stories with subtasks where there are multiple resources (mostly a dev and then qa team member). In the case where we use subtasks we are estimating time at the sub-task level and NOT at the story level (the story level is a sum of the sub-tasks). Unfortunately when people log time against there subtasks the burndown is not burning down; subtask time entry is not be logged. How can I configure this to work?
A couple of things to check :
Hi - thanks for your response, the settings are and have been exactly as you mentioned above and still no dice. Logging on sub-tasks doesn't impact the burn down (red line).
We recently switched over to estimating on the sub-tasks over story level estimation so this is a new concept to the team.
If you look at a parent issue where you know some time has been logged on one of it's subtasks, do you see something like this?
Then also look below the burndown chart and do you see lines like this?
The right hand column is the remaining time in the sprint - possibly attach a similar screenshot for a few of the rows.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs