I try to understand how to think about that.
What are the three, most important questions, to ask about each state?
Any suggestions ?
Most important 3 questions when designing a workflow
Moderators: Developer, Contributor
-
powerboots
- Posts: 26
- Joined: 19 Jan 2007, 01:27
Most important 3 questions when designing a workflow
While adopting Mantis, eventually you come to the question how to customize the workflow.
I try to understand how to think about that.
What are the three, most important questions, to ask about each state?
Any suggestions ?
I try to understand how to think about that.
What are the three, most important questions, to ask about each state?
Any suggestions ?
-
hmackiernan
- Posts: 18
- Joined: 17 Feb 2006, 19:23
- Location: San Francisco, CA
Hello 'boots:
I'll take a whack at this, but this is just off the top of my head so your mileage may vary:
- Which states correspond to critical phases in your development process?
If moving a bug to state VERIFIED (for example) triggers a release to a client, then you should be darn sure the defects are actually fixed -- do you want to require an intermediate state (maybe FIXED) that anyone (any developer) can move bugs INTO but that only a QA analyst, project manager, whoever can move OUT of into 'VERIFIED'?
Ok that's all I can think of at this moment... anyone else?
---
hmackiernan
SF CA
I'll take a whack at this, but this is just off the top of my head so your mileage may vary:
- Which states correspond to critical phases in your development process?
If moving a bug to state VERIFIED (for example) triggers a release to a client, then you should be darn sure the defects are actually fixed -- do you want to require an intermediate state (maybe FIXED) that anyone (any developer) can move bugs INTO but that only a QA analyst, project manager, whoever can move OUT of into 'VERIFIED'?
Ok that's all I can think of at this moment... anyone else?
---
hmackiernan
SF CA