Story point count in backlog overview is inconsistent

Sonal April 19, 2022

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

Screenshot 2022-04-25 at 15.42.03.png

Extra Info

  • I have 3 statuses with resolution = DONE. Let's say status A, B and C. I see that status C is not being counted as DONE on the backlog. Even though in the workflow and everywhere else (sprint reports, charts) it is processed correctly as done. Also in the columns on my board, the status is on the last column and configured correctly.
  • This was working as expected until a few days ago. Suddenly, I noticed I marked something as done with status C and that it did not reflect on the backlog view anymore. I don't know if something caused it specifically.

 

3 answers

1 vote
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 19, 2022

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.

Sonal April 20, 2022

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.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 20, 2022

Does the issue that is not being counted as done have any open subtasks?

Sonal April 20, 2022

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 

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 21, 2022

Ok, and are all the "done" subtasks in the last column on the board?

Sonal April 22, 2022

indeed

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 22, 2022

And all the sub-tasks are shown on the board, you're not excluding any for some reason?

Sonal April 25, 2022

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 >

Screenshot 2022-04-25 at 15.42.03.png

  • This is the status of category DONE and as you can see, it counts as blue (in progress)
  • Everywhere else - be it any report, the board, etc - it counts as DONE as it should.
  • I have other custom statuses too .. they all work fine and as expected. Only for this very specific one ... it won't count as green (done) here

 

Any ideas?

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 25, 2022

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.

Like Jack Brickey likes this
Sonal April 25, 2022

The status is in the last column of the board - always has been. Subtasks as well. I am certain. That's why I am totally baffled.

Sonal April 25, 2022

For the one in my example

  • main ticket with "Ready For Integration" and child ticket is "Done"

 

Screenshot 2022-04-26 at 08.55.24.png

  • On the Board, everything on the last column

Screenshot 2022-04-26 at 08.56.00.png

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 26, 2022

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.

0 votes
Ajini Sahejana Perera
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 1, 2024

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 :)

0 votes
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 19, 2022

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?

Sonal April 19, 2022

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

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 19, 2022

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?

Sonal April 19, 2022

@Jack Brickey 

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.

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 20, 2022

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.

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 23, 2022

@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.

Suggest an answer

Log in or Sign up to answer