Resolved vs Done - Burndown will happen much later 4-5 days after Sprint starts

[Shalvika Sood]

This question is in reference to Atlassian Documentation: How do Story Points get burnt down and reflected on the Burndown Chart

We have 'Resolved' and 'Done'. A Story is completed only after it is marked as DONE. This means that the progress will NOT be gradual as everyone seems to think so. A developer resolves it, QA verifies it and then finally PO marks as Done. This means that a story will typically get 'Done' only after 4-5 days. So how does the step ladder come into play?

The story-point burndown does not show a daily burndown or progress of tasks. How can we see that?

[Tj Tyrrell]

We are having the same issue and are looking for a similar answer.

Currently we have two boards, a development board and a releases board. The Development Board (Scrum) has all statuses that are QA and Release prep as marked as Done. That is where the Releases Board starts.

There are major disadvantages as if an issue fails QA (specifically when they fail integration testing), it gets rejected and then doesn't show back up on the dev board. We'd like to all then use the same board to progress tickets.

However, we'd like the Burndown chart to reflect development and not release (as the OP lists). Is there any way to map the burndown chart against custom statuses and not the right-most column on the Sprint board?