Done Sprint Ticket to a New Board

[Marlon B]

We use a Scrum board with final status = Done (Set Resolution)

When the sprint is complete, we need those tickets to move to a Kanban board for User Acceptance Testing.  How can we achieve this?

[Jack Brickey · Accepted solution]

well it depends on your workflow TBH. If "Done" status ultimately goes to subsequent statuses, e.g. UAT which then can say move to "Closed" then you can certainly do this and I have done something similar before (see below). Now if Done is in fact the final terminal state then this wouldn't make sense as you couldn't transition to final closure.

Example solution:

assume you have a workflow that looks like this - To Do > In Progress > Done > UAT > Closed

then you might have...

Workflow status for development: To Do, In Progress, Done

Workflow statuses for QA: UAT > Closed (can transition from UAT back to To Do or other if it fails)

Now for the boards:

Dev Scrum board JQL -  project = xxx and status not in (UAT, Closed)

QA Kanban board JQL - project = xxx and status in (Done, UAT, Closed)

so you see that "Done" will be on both boards. It will be the right-most in the Dev Scrum and the left-most in the Kanban. Done equates to 'to do' for the QA phase and hence belongs on the left.

[Marlon B]

Does your example still provide for generating metric for tickets when the Sprint is closed, "Done"?  That's one of the issues I'm having trying to figure this out.

UAT is completely separate from the Scrum, so tickets will remain on the Kanban board until it's scheduled and complete.  Available UAT tickets are based on tickets that are "Done" from Sprints.

[Jack Brickey]

yes it should since scrum boards base the metrics off the right-hand most column. I would likely consider a more complex "resolution" implementation, e.g. when moved to Done set the Resolution to say "Dev-complete" and then when moved to Closed to maybe "resolved, complete, done, etc.".

yes the boards overlap w/ Done, e.g.

Scrum - To Do >> In Progress >> Done

Kanban-                                           Done >> UAT >> Closed

[Marlon B]

Thank you for your time and responses.

I will give this a try in the morning and report back.

[Jack Brickey]

Another option to consider is to use automation to create a new task altogether when an issue is moved to Done w/ a specific resolution that indicates it is ready to be tested. You can use smartvalues to pull in the triggering issue's summary, etc. and link the two. Personally, I prefer separate issues as it retains some since of ownership. You could even have the original issue 'reopen' if the QA issue is transition to 'failed'.

just a thought.

[Marlon B]

Hello Jack, I created the GAT board as suggested using the method below, and the tickets display as expected based on the filters.  

Scrum - To Do >> In Progress >> Done

Kanban-                                           Done >> UAT >> Closed

Thank you very much.

[Marlon B]

This didn't work as planned, as soon as I closed the Sprint, all of the tickets were removed from the GAT Kanban board.  Jira states, .... the issues have been filtered out by the chart refinements.

Should I remove the resolved checkmark from the Done column on the Scrum board?

[Nic Brough -Adaptavist-]

I think you might be misunderstanding the boards - they are not containers for issues, they are views.  An issue does not go on to a board, or move off it, an issue is selected for, or not selected for a board.

When you closed the sprint, this changed something on the issues in the sprint that meant that they were no longer selected by the Kanban board.

Do NOT remove the resolved checkmark on the done column - this will break things in other ways, because you would now have "quantum" isssues - ones that are resolved and unresolved at the same time.

You will need to take a good look at the filters for the Scrum and Kanban boards to see why things are not being selected by the board.

[Jack Brickey]

yes. I suspect the Resolution is interfering w/ your plans here. you can clear one and verify this is the cause.

[Marlon B]

I do understand that the boards are just views, I don't understand why the view has changed when the Sprint closed.

My filter is simple: project = "project" and issuetype = "story" and staus = done.  The issues on the Kanban board where visible while the Sprint was active.  Once the Sprint closed, they no longer appear on the Kanban board.  I can still view these in the issue navigator.  What am I not understanding about the board? I may be missing something simple.

I thought the issue was the Kanban board sub-filter, removed it, but didn't resolve the issue.

[Marlon B]

OK, now I'm even more confused.  I just went back to the Kanban board and the tickets display as expected.  I can't explain it, they were not there this morning.

Thanks again for your input, I appreciate your time.