How to manage sprints with multiple boards

[Nina Andrić]

We would like to have 2 boards in 1 team - 1 for developers and 1 for QAs. The sprint is going to be the same, but "Done" for developers (in our case "Ready for branch testing" status) and "Done" for QAs ("Resolved" status) is different, therefore we would like to have 2 boards and have a sprint report that will treat all "ready for branch testing" and "resolved" tickets as completed in that sprint. I have created 2 boards, and put these 2 statuses are right-columns, but the Sprint report is saying that nothing was completed in the sprint. Can someone help me with this and advise how to achieve what we wanted? Thank you!

[Danut M _StonikByte_]

Hi @Nina Andrić,

Hm, this should work. For the DEV board you should map the "Ready for branch testing" and "Resolve"  statuses on the last column of the board. For the QA board you should map the "Resolve" on the last column of the board and map "Ready for branch testing" on a mid-column (In Progress) of the board.

Danut. 

[Nic Brough -Adaptavist-]

It can't work - the question is about having a single sprint, not two separate ones.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

This won't work - you don't really only have one team here, you've got two, and boards and sprints represent teams.

If you really want the sprint reports to work, and only have one team, then you can't have "development done".  The whole team needs a single definition of done, which means it's been tested - the whole principal is "no-one on the whole team needs to do anything more about this issue".  One board, and the users know which columns are more important to their areas of expertise.

So, you need to decide if you've really got one team, or two (Dev and QA)

[bduncan]

Agree, if you want a single native report to work then all the work needs to be together. It is a more common practice to staff the team to get to done-done.

All that said if you are limited on how teams are structured and your intent is more about monitoring rather than reporting you could consider a board across projects (aka. teams):

1. Create a filter something like to view current work:

   1. sprint in openSprints() and project in (developers, qa)

2. Create a filter something like to view prior work:

   1. sprint in closedSprints() and project in (developers, qa)

3. Create a board using each of the custom filters, and configure columns as needed.