Using Kanban and inculding the QA process

Guy Levin April 13, 2015

Hello,

We want to use kanban and inculde the QA process in the folowing way:

Those are the columns:

Backlog ->  Selected for Development -> In Progress -> QA -> Done

 

And there is another lane, lets call it "Not Passed QA" that is spose to hold the issues that are retuened from QA

When the qa moves the issue to the "Not Passed QA" lane it should be assigned to the last person worked on the issue before the QA.

So the question is how to add a lane and workflow to function that way

Thanks !

 

1 answer

0 votes
Peter Bengov
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 13, 2015

The question regarding the Not Passed QA "lane" is more process-related. This can be done by applying a swimlane or creating a separate status for you to use. 

  1. As for Swimlane, you can have a transition called "Failed QA" that will move the ticket to an existing status (In Progress) but will also have a post function that will mark some flag field which will show the ticket in a separate swimlane then other In Progress tasks.
  2. As for a status, you just create a new status and link a transition from QA to that new status. Of course adding a new column to your Agile board.

With regards to assigning the ticket to last person who worked on that issue:

  1. Create a user picket field (you can call it Developer). It doesn't even have to part of your screens.
  2. In the transition between Selected for Development to In Progress add a post function called Copy Value From Other Field. There copy the value from assignee field to this new field (assuming the assignee is indeed the developer).
  3. Later, when using the transition from QA back to In Progress (or another status you have used) - use the same post function just the other way around (from Developer to Assignee).

Note: this post-function I've mentioned might be part of a plugin we are using.

 

 

Suggest an answer

Log in or Sign up to answer