How to create burndown charts based on Passes QA status

Vincent Massa February 22, 2024

We are a small shop that have been making the slow, painful process of Waterfall over the past few years. Likewise, we do not have a CI/CD environment yet. We deploy every three weeks following our development and demo sign off process. Once we are done, we do a deploy that night and the following morning we move all tickets that passed the demo to Deployed. Because of this, the stock burn down report does not give us up to date information through the sprint. 
I have been searching but so far have not been able to find a way to create a burn down chart that is keyed to our passes QA column/status.

 

Any ideas?

2 answers

1 vote
Danut M _StonikByte_
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.
February 25, 2024

Hi @Vincent Massa,

This can be easily done, without being necessary to alter your agile board, by using the Sprint Burndown Burnup Chart gadget offered by our Great Gadgets app.

This gadget allows you to set multiple statuses as done. So all you have to do would be to add your Passes QA status to the list, like this:

image.png

And the chart will be displayed in a second. You can configure it to calculate by any type of estimate or issue count.

image.png

Similar to this, by using the same app, you can display Team Velocity Chart and Release Burndown Burnup Chart.

You have 1 month of free trial and it is free for up-to 10 users.

Hope this helps. 

Thank you,

Danut Manda

0 votes
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.
February 22, 2024

Welcome to the Atlassian Community!

The short answer - put the "passed QA" status in the last column of the team's board.

Note that I said "team" - your deployment people may have a different definition of done, and so should probably be using a different board to manage that.

Given a workflow that should take issues through

To-do -> in-dev -> ready-to-test -> demo -> passed QA -> deployed

Then your team probably needs a column for each of those status, except passed-qa and deployed - those should both be mapped into the last column on your team's board

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events