How to prevent issues from showing as reopened on burndown report.

[Dustin Cannon]

I currently have 2 boards active under the same project. 

Board 1 = Development (Scrum)
Board 2 = Product UAT (Kanban)

The "Done" status for the Development board is "Ready for STG Deployment" (Done type)

The first status for the Product UAT board is "Ready for STG Deployment" so the issues move automatically between the board and the Done status is "Deployed on Production"

Issue: Whenever I am moving an issue through the life cycle on the Development board and move to the Ready for STG Deployment "Done" status, on the burndown report it shows the issues as completed and then re-opened once the issue moves to the other board which throws off reporting metrics. 

Goal: I need to be able to have the issues on the Development board burn down report remain completed when issues are automatically being transitioned to the Product UAT board and through the other status on the Product UAT board. Once the issues moves to the Product UAT board, I do not want the burn down report on the development board to be updated. 

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

There's a bit of a misunderstanding here.  Issues do not move between boards.  Boards are a view of a selection of issues, not issue containers.

I can see you've partially understood this, because you've got two boards selecting things in certain status, but the other thing to understand is what "done" is on a board - it's the last column.

Your development board is reporting the items on the UAT board as open because they are no longer in the last column on it.

There's a simple fix - add all the status that are mapped in the UAT board to the "done" column on the Dev board.  That way, the Dev board will continue to see them as done, and it won't cause "removed from sprint".  You might set up a quick filter to hide them.

[Dustin Cannon]

Thank you Nic for the deeper explanation and the solution, this worked as expected.