Workaround for Burndown Charts

Satyaki Deb

Hi Everyone,

I am new to JIRA. We are working on an Agile Scrum Project where the Definition of Done is read as UAT Completed. We have completed 3 Sprints as of now and the 4th one is ongoing. UAT is supposed to start for all the 4 sprints together and hence, all the developed stories are currently in QA Completed status. Is there any workaround by which we can have a burndown chart for the sprints based on the QA completed status? If not is there any other charts we can use to accomplish this requirement to track down the effort expended? I have attached a partial snapshot of the workflow for reference.  

Tarun Sapra

Hello @Satyaki Deb 

Your requirement is a pretty common one. 

 Is there any workaround by which we can have a burndown chart for the sprints based on the QA completed status

The easiest way to achieve this is to make sure the status "QA completed status" is the *right-most status* on the Scrum board. In Jira board configuration you can map columns to the workflow statuses and if your workflow status (QA completed) is mapped to the right-most column of the baord then when the issue moves to this status then it will be considered done by the board and hence reflected in the burn-down chart.

For the statuses in your workflow after the QA completed status you can create a Kanban board to track the progress of the release as the later statuses are more related to releases hence you can split the workflow across two boards. First can be the scrum board and then it can be the Kanban board.