Redifine the ticket process in assembla following the QA/dev team reorganisation
Current ticket lifecycle is available here https://www.assembla.com/spaces/meveo-enterprise/wiki/Processes, chapter Community tickets lifecycle
New ticket lifecycle (Opencell side), feel free to comment...
i think we need to merge test designer and test reviewer roles in your graph
also i would not serialize test and doc but do in parallel
The problem I see with this diagram is that normally when a developer is working on a ticket and coding he also develop a soapUI test, because it's hard to know if the code is running correctly without testing it. So I think test plan creation should be at the start of the process when a developer accepted a ticket.