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; } } }

How to change the trigger for the burndown chart

Tim Lange_1ql3z4

Hello!

We would like to trigger the burndown not based on the last column, but on a column before that last one.

Goal: allow the dev team to monitor their progress before bringing all stories of a sprint to the review meeting where the PO sets the stories to DONE as the final stage.

Thanks,

Tim

Accepted answers

Nic Brough -Adaptavist-

There is no way to do this.

The last column on a board is "done", and hence gives you a burndown.

Your goal here is perfectly valid, but botching status so that things are done but not done is not the right way to achieve it.

All comments

Nic Brough -Adaptavist-

There is no way to do this.

The last column on a board is "done", and hence gives you a burndown.

Your goal here is perfectly valid, but botching status so that things are done but not done is not the right way to achieve it.

Tim Lange_1ql3z4

Thanks for the clear answer!

I'm just wondering how others do this in similar setups. Do the devs set stories to DONE before presenting them in the sprint meeting? Our goal is to set stories in the review meeting to done once they meet all criteria approved by the PO. 🤔

Jack Brickey

i have used a method of splitting my workflow across two boards, i.e. dev in scrum board w/ last column = 'ready for QA' and a kanban that starts with 'ready for QA' and ends with 'Done'. Not a big fan but it did serve the purpose. Maybe a similar approach would work here?

Tim Lange_1ql3z4

Thanks Jack!

This way the burndown chart goes down once the devs set the stories to the most right column?

And the stories are DONE once QA sets it to DONE in the second board and thus the stories are entirely closed?

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

burndown

chart