How does the reports work at the end of a Jira Sprint when Status is not in Active Sprint Board?

Calvin
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.
March 4, 2024

Hi all, basically we have items we place into a sprint that we estimate with story points. That works all good and on the sprint report when the sprint starts it does have a max number of stories.

Now as I move it along the sprint it goes to "Test" at this point we want to call it in the sprint as complete (even though the item isn't). So we placed the Test on the right side at the end of the sprint. This then subtracts the number of story points in the report (all good).

This works fine so far, but then when we move it beyond test to say "into Production" or "Production Test" it then places those story points back in and says its no longer complete because its not in that final column anymore.

Is there anyway around this? Or would I have to place every item after "Test" into that final column? (For some reason Team really doesn't want to do it)

1 answer

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 4, 2024

Hi Calvin,

The Scrum boards are very simple, they just regard the last column as "done".  They do not really care what the status is, but if your issues are not in the last column (including not being on the board at all), then they're not done.

"Done" is not as simple as a binary flag though.  It is not quite "subjective vs objective", but it is very team-focussed.  Some teams "done" may be other teams "to do".  "Done" on a board means "the team using this board to drive their work has finished, they have no more to do with the issue".  But that does not mean that another team has nothing to do.

When you have steps beyond the last status that your team cares about, there is a simple fix - include the following status in the team's "done" column.

I'm guessing at your workflow here and simplifying, but say the ideal flow is something like:

New -> In-dev -> ready-to-test -> in-test -> test-passed -> deployed

  • Your DevOps team needs a board that just has:
    • to-do: tests-passed
    • done: deployed
  • Your testing team probably wants:
    • to-do: ready-to-test
    • in progress: in-test
    • done: test-passed, deployed
  • Your delopment team probably wants:
    • to-do: New
    • in progress: in-dev 
    • done: ready-to-test, in-test, test-passed, deployed
Calvin
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.
March 6, 2024

Thanks Nic, I was sort of hoping to stay away from placing it in the final column a bit as users start trying to push it through the workflow in that final column and in some cases we have a few flows you can go to and users don't check and accidentally move it to the incorrect one.

But your details were very helpful, especially in letting me know that this really is the best option available, as when passed what the development team wants as done, not having those statuses in that column means the reports are now broken, so they have to be in there! haha.

Suggest an answer

Log in or Sign up to answer