Burndown Chart reflects progress when tix are moved to QA board

[Alex Bakhteyev]

Background: We have 2 boards under 1 project (Dev - Scrum and QA - Kanban).

Dev board Workflow: To Do, QA Failed, In Progress, Blocked, In Review, Dev Complete, Done.

QA board workflow: Dev Complete, QA Ready, QA In Progress, QA Blocked, QA Failed, Done 

Problem: when transitioning tickets from Dev Board to QA Board ( status Dev Complete to QA Ready), it got reflected as burndown. The issue is that testing supposed to happen to reach Done status and only then it should reflect on Burndown chart.

Can you guys help how to fix it so that Burndown chart would show progress only when the status Done reached. 

[Trudy Claspill · Accepted solution]

Hello @Alex Bakhteyev 

Welcome to the Atlassian community.

The burndown chart will reflect the issues based on their appearance in the board. When you transitioned the issue to QA Ready, that removed the issue from your Dev board. To fix that you will have to have all the issues in your QA board assigned to columns in your Dev board. You could create a single column in the Dev board between Dev Complete and Done, and map to it the QA Ready, QA In Progress, and QA Blocked statuses.

[Alex Bakhteyev]

do you mean i have to cerate 1 additional column and map it to 3 statues ( QA Ready, QA In Progress, and QA Blocked statuses) . How can I do it ?

[Trudy Claspill]

Hello @Alex Bakhteyev 

That can be done by a user that is an Administrator for the board 

Click the ... button in the upper right above the board and select Configure board.

Select Columns from the list of options. That should show you the board columns and the statuses mapped to each column. There should also be an area labeled Unmapped statuses. Do you see the QA statuses in that area?

If you do look for an Add button above the columns on the right. Use that to add a new column and drag the column to the desired position. Then drag the QA statuses to it.

If you don't see the QA statuses in the Unmapped Statuses area, then they are likely being excluded by the board filter, and then that will have to be changed first.

[Alex Bakhteyev]

Thanks @Trudy Claspill

Yes, I can see the unmapped column with QA statuses. Just curious how would you call that new column on dev board? 

[Alex Bakhteyev]

also if tickets will be transitioned to this new column, would they be automatically added to QA board in proper status so that QA would see them ? 

[Trudy Claspill]

You can give it any name that makes sense to you and your team. The column name doesn't have to match the name of the statuses.

[Trudy Claspill]

When issues are dragged to a column that has multiple statuses, each status will show as a highlighted area ind the column. The card should be dropped in the appropriate status.

Boards are just a way to visualize and manipulate the issues. An issue can be displayed on multiple boards at the same time based on the board filters and status/column mappings. So, yes, when the card is moved to a QA status on the Dev board it will then also be visible on the QA board.

[Alex Bakhteyev]

Awesome! Thank you @Trudy Claspill . that worked!