3

2

I'm trying to build a semi-complicated workflow that was designed by a QA specialist. The workflow follows a typical developer cycle with the developer ending his responsibilities at FIXED.

  1. Developer finishes work and marks FIXED automatically assigns the bug to the QA dept who will immediately take action and begin testing.
  2. QA marks TESTED if the bug was actually fixed or
    1. QA marks REOPENED to reject and send back to Dev.
  3. QA marks VERIFIED
  4. Release Manager marks RELEASED which closes the bug.

I'm not sure if I'm going down the wrong path here, can someone check my sanity? Do I need QA plugin?

flag

1 Answer

2

I think your workflow matches FogBugz fairly well. I assume you've installed the Workflow plugin? Create a new Active status, called (say) "Active (Test)."

  1. New cases are Active
  2. Once coding and review are complete, cases become Active (Test)
  3. After testing, cases are opened (back to original Active) or Resolved. Don't bother with a separate "Active (Reopened)" status; it doesn't serve any purpose I can see.
  4. Once case has been released, it is closed.

You could also have separate cases for Resolved (Awaiting Release) and Resolved, but I think closing them on release simplifies things. The WorkFlow plugin will allow you to assign cases automatically on changing status.

link|flag

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.