Workflow issues

[Jakov Kalashnikov]

Hello the best community ever! 

I do have quite a complex question, however I believe you could help me solving that. In my project I do have a large team of Developers and QA engineers. Both parties wanted to separate the boards to have a better view and transparency on their daily routine. 

Workflow is pretty straight forward : 

Open > In progress > Code-Review > Ready 4 deploy > Staging > QA > Released

The issue is the fact, that Developers want to see the Story points being burnt in the Staging status (to have the better burndown chart and also be proud of their achievements as QA process is quite complex and takes time). 

At the moment what I get is a flat burndown with the Issue completed and Issue Reopened in the Event detail section of a report, because the issue is transitioned to the QA furtner. Is there any available solution for this? 

Thanks in advance! 

[Stephen Wright _Elabor8_]

Hi @Jakov Kalashnikov 

Board reports work off the last status in the most right-hand column - could you limit the Developers' board to have Staging as their "Definition of Done"?

QA would need to be on a separate board (with the 3 statuses, Staging > Released) - but if the QA process is complex and takes time, isn't this outside of the Dev team's DoD anyway?

Ste