Provide customizable work flow for Kanban and Bug Tracking
Flow dependent processes like Bug Tracking and Kanban should have customizable work flow mechanism to enforce their processes respectively. For example:
a) when a bug is submitted, it should always go to QA for verification before sending to developer for bug fix,
b) a QA rejected task/user story should always be returned to developer instead of sending for further system test
3
votes
morgan.chan
shared this idea
-
Robb Lovell commented
You should be able to see "In QA" as a column on the agile board, which means that the columns on the agile board should be able to be customized.