nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I change the Done condition for reports like Burndown and Epic Report to another status?

Franziska Buch

It is my team's habit to move completed tickets to Done only in the sprint review session. This is to ensure that acceptance criteria etc have been met. Until that time, actually compelted items are parked in a special review columnThis, however, renders burndown charts for the current sprint useless since the Done-condition isn't met until the very last day of the sprint. Is it any way possible to configure the report so that a different status qualifies as the Done criterion, as far as jsut the report is concerned?

Accepted answers

Jack Brickey

These reports are based off the right-most column of your board. What status is in that column?

All comments

Evgenii

Hi, @Franziska Buch

Welcome to Atlassian Community.

This behaviour, about which you're talking, depends from Resolution, not from status. It's two different entities.

You can change workflow, and add postfunction to set Resolution on transition to status, mapped with "special review column". It's not a very correct workaround, because resolution is set usually only when issue is completed, but it will work in your case

Jack Brickey

These reports are based off the right-most column of your board. What status is in that column?

Rebekka Heilmann (viadee)

You can find the docu on this here: View and understand the burndown chart | Jira Software Cloud | Atlassian Support

@Jack Brickey correctly summarised what Atlassian states as: "The Burndown Chart is based on your board's column mapping. An issue is considered to be 'To Do' when it is in a status that has been mapped to the left-most column of your board. Similarly, an issue is considered to be 'Done' when it is in a status that has been mapped to the right-most column of your board. See Configuring columns for more information."

Rebekka Heilmann (viadee)

In the reports it actually doesn't use resolution (I know, it's quite inconsistent to behaviour anywhere else in Jira).

Trudy P Claspill

Adding to this...

Because the Burndown chart is based on the right-most column of the board, to get it to burn down issues based on another Status you would have to map that other Status to the right-most column of the board.

You can have multiple Statuses mapped to the right-most column.

Note, though, that when the sprint is Completed all issues in the right-most column will be considered "done" regardless of their actual Status value. So if you mapped the "special review column" Status into the right-most column, then issues in that Status would be considered "done" when the sprint is Completed, even if you didn't transition them the the actual "Done" status. Those "special review" status issues would be removed from the board and not moved to the next sprint, just like the Done issues.

Nic Brough -Adaptavist-

No, it does not. Resolution is not used in boards. All that matters to a board's definition of done "is it in the last column?"

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud