I am in a team managed project. We use the scrum board for two week sprints.
My problem is that
In the backlog view, I do not see an accurate "story point estimate" count for the Resolution DONE
If I look to the sprint burnup report, I see 27 story points DONE
If I look to the sprint in backlog, I see 15 story points DONE
I would like to see the sum of all story points with resolution = DONE in the backlog view counted in the green (done) category.
See example
Extra Info
Ah, hang on, you say "I have a separate workflow for subtasks"
Are you putting sprint estimates on sub-tasks? This does not work - sub-tasks are part of their parent, not sprint items, so burn reports ignore estimates on sub-tasks.
hey that was just extra info about the subtasks. I am not putting estimates on the subtasks and the problem is unrelated to them. The burnup report is okay and consistent. The problem is in the backlog view where a done status is not being counted in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does the issue that is not being counted as done have any open subtasks?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hey @Nic Brough -Adaptavist- that's unfortunately not the case.
If that would be the case, it would still be an anomaly (as the other resolution done do get counted even if they have open subtasks)
But in this case, even if I mark all the subtasks as DONE .. the parent as resolution DONE, it still does not get counted in the done circle of story points
FYI @Jack Brickey
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, and are all the "done" subtasks in the last column on the board?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
And all the sub-tasks are shown on the board, you're not excluding any for some reason?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Nic Brough -Adaptavist- @Jack Brickey
I am not convinced that we are moving closer to the root cause. I'd like to show an example >
Any ideas?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This will happen if the status is not in the last column on the board, or it has sub-tasks not in the last column on the board.
The status and resolution are not important here, it's the columns that matter.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think we need to see the raw data - could you search for the issues in the done column, and show us the list - Issue type, issue key, and the estimate field are the only three columns we need to see.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm facing the same issue right now; do you think setting the resolution is related to this matter somehow? Let me know if you've found a way around it :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sonal ,
burn down should be triggered by every status that is mapped to the last column in your scrum board. You mention three different done statuses are they all map to the last column?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hey @Jack Brickey yes, the 3 status with resolution DONE are all mapped to the last column and they appear correctly on the scrum board too. So no inconsistencies there
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Sonal. Indeed I would expect the burn down chart to illustrate the story points from each issue in that column. One question though is this associate with multiple projects or one and are we talking CMP projects or TMP?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is just associated with my project, so only one and it's a team managed project.
Indeed - It was working as expected. Now it ignores one of the DONE status in the count. Just that one specifically..
I have a separate workflow for subtasks and another workflow for all other issue types - don't think that should affect the behaviour either ways but that seems to be the only change I have done in between it was working all fine and now its broken.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So I use TMP rarely and not for SW/Scrum. I certainly find it odd that only one of the Issuetypes isn't working and that it was previously. Has this occurred on more than one sprint? You mention subtasks were added under new workflow. For the status not being counted associated with issues with subtasks? I'm thinking that this change you made is the smoking gun and Nic's input is on the right path.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sonal I think @Nic Brough -Adaptavist- is on the right path here. One thing I would be interested in here or at least what I would look at if I were you would be to interrogate the issues that are 'missing' from the backlog view. If you look at your burn down chart and reports and inspect every issue with it burn down then compare that to your backlog exactly where is the misalignment? That is which specific issues seem to not be captured in the backlog. Hopefully that's not a extensively long list of issues that you have to go through but at this point I think it's worth dissecting the situation more fully.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.