Bug cards in QA:doing are being moved back to "Ready for QA"

[Ursula Junque]

I've moved two bug cards from "Ready for QA" to the "QA:doing" lane, to work on them, and I've noticed that the automation script is moving them back to "Ready for QA", probably because it's using the data in the bug to infer status, not the card. I've only noticed this happening with bug cards.

(bugs are lp#1522389 and lp#1508110)

This problem could be "solved' in two ways:

1) Creating two "sublanes" in Ready for QA: todo and doing. Cards "Ready for QA" would be placed in "Ready for QA:todo" and all cards that QA is actively testing would live in "Ready for QA:doing". This way it's easy to know what QA is working on, testing wise, and developers/dpb don't have to scroll all the way to the bottom of the board to try to infer what card among the many "QA:doing" is relevant for them. It also helps us in the QA squad to tell what are the testing tasks and what are our own development tasks in progress.

In this scenario, once the card is in "Ready for QA:doing" bot wouldn't touch it until we're done QAing it. We (QA) are still not clear what's the next step in the process after QA tested something, if the flow is lp->kanban we can add a tag to the bug so the card can be moved to "Release Ready", and another tag for it to be moved back to the squad "In Progress" in case we find a blocking issue.

2) Modifying the script in a way it won't touch the card if it lives in QA:doing.

I like option 1) best for the reasons mentioned, but I'm fine with either one if it stops resetting the "QA" status. :)