Enforcing development cycle through Bugzilla [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.

---

Want to improve this question? Update the question so it focuses o开发者_高级运维n one problem only by editing this post.

Closed 6 years ago.

Improve this question

I work on a project with a pretty formal development process: there's a list of required documents, from requirements to design to testing to user documentation. We're trying figure out how to make sure all feature development goes through all the stages.

One idea is to use Bugzilla's Status field to capture the workflow; we'd add the following status entries and make bugs go through all of them before being resolved:

UNCONFIRMED
NEEDSREQUIREMENTS
NEEDSUIDESIGN
NEEDSDESIGN
NEEDSIMPLEMENTATION
NEEDSDOC
NEEDSTEST
RESOLVED
CLOSED

Has anyone tried capturing a development process through Bugzilla like this? Is there another approach or tool that would be a better fit?

---

You should use requestable flags. For example: a flag called "ui-design." Then you set it to "?" to mean "needs UI design" and "+" to mean "has UI design" or "-" to mean "doesn't need UI design".

---

I think you would be better off using flags for capturing this workflow. Having a busy state transition diagram through which you try to enforce workflow would sometimes be annoying when there's some valid reason for handing one bug a little bit differently.

For example, you could have two flags needs-ui-design and ui-design-complete to describe the status of UI design. UI designers could easily search for bugs that have needs-ui-design set to + but that do not have ui-design-complete set to +.