Can a 'Done' issue at the end of a sprint reflect on another board?

[Tyler Guthrie]

Hello, 

I'd like to have three boards - Design, Development, and QA. I'd like to track the velocity of these teams automatically in Jira. That said, I'd like any stories in the 'Done' column for these boards to reflect on the NEXT BOARD... is this possible? If so, how do i accomplish this (currently using Team boards and not Company boards).

More Detail....

1. Story Picked up and worked on with Design

2. Story in 'Done' in the Design board

3. Close Sprint after 2 weeks

4. Story automatically goes into backlog for Development board

5. Story Picked up and worked on with Development team

6. Story in 'Done' in the Development board

7. Close Sprint after 2 weeks

8. Story automatically goes into backlog for QA board

.... 

all the while, tracking the velocity of each of these teams individually...

thoughts?

[Trudy Claspill]

Hello @Tyler Guthrie 

You said you are using Team Boards, not Company Managed boards. Do you mean that each of these teams has their own separate Team Managed project? Or are the teams working in one shared Team Managed project?

Are your teams using Kanban or Scrum boards?

Those answers impact the viability of @Walter Buggenhout 's suggestion.

[Walter Buggenhout]

Hi @Tyler Guthrie,

Just did a quick drawing to try and illustrate: if you design the workflow for your story like this:

You should be able to create 3 boards that handle each part of the process, as I tried to indicate above the statuses (Design / Dev / QA).

Just map the statuses that are relevant for each part of the process to the columns of your board. Make sure that the final status of each phase is both the rightmost column of the first phase, and the leftmost column of the next phase. That way, the end state of one phase is also the backlog for the next.

The dotted line that goes from QA to Ready for Dev is a transition that puts an issue that did not pass QA back in the hands of the dev team.

Most likely you'll need to put a bit more thought in the details, but the idea behind this is definitely a way you could address this.

Hope this helps!