Burndown chart on issues that are Dev complete but not yet tested

[Nick.Falconer]

Hi,

I have a project where we use a "Dev Complete" column to put all the sub-tasks that have been completed by dev and peer reviewed, but are not ready for testing yet. I would like a burndown chart that 'burns down' the tasks and stories once they reach this status (or leave the In Dev status). With the standard JIRA burndown report, the story is not burned down until QA move it to done, and this isn't accurately showing Dev velocity (even though Dev work is done). I want to report on Dev velocity only not including QA in this. If there are any alternative reports that may do this, that would also be great.

[Petter Gonçalves · Accepted solution]

Hello @Nick.Falconer

Welcome to the Atlassian Community!

Per your description, I understand that you want a report that will consider an issue to be completed when it reaches the "Dev Complete" status, which is not the final status o your issue. Is that correct?

Unfortunately, All Jira Agile reports consider an issue to be resolved when it is in a status that has been mapped to the right-most column of your board, added with a valid resolution and a status in the Done category.

That being said, I believe the best practice to achieve the goal you are looking for would be to create different issues for each team (DEV and QA), instead of using the same issue to map all the progress from DEV to QA. Explaining better:

1. You would use different issue types and workflows to map the progress of each team, optionally using different boards/Sprints to track their work.
2. Then, use the Issue Link feature to set the relation between the DEV and QA Issues, optionally linking them to a single Epic if you want to track the progress of both teams in a single issue as well.

Let us know if you have any questions.

[Nick.Falconer]

Hi Peter,

Thank you for the detailed response, you've answered my question.

Many thanks!

Nick

[Petter Gonçalves]

You are welcome, Nick! 

[Jay Warshaw]

@Petter Gonçalves Looking for advice, was thinking about creating automations to clone a task when it gets to Dev Done on the DEV track, into a ToDO for the QA team. Any thoughts about that?

[Samer Mansour]

Can we make a change request for the burndown charts to use status category over the column ordering?

Or on the burn down report page allow a drop parameter for column ordering vs column category. That way if Atlassian doesn't want to change the existing board functionality because all the academics and scrum leaders of the world would complain, then at least it would still allow our teams to customize the report with that param for our needs.

I suspect if you delivered this functionality, you could measure clicks there is a part of the community that would prefer this way.