New Default Bugzilla Workflow?

[avatraxiom]

I have proposed that Bugzilla have a new default status workflow. I wrote my reasoning in a message on the mozilla.dev.planning newsgroup, originally as an argument for a workflow that Mozilla should move to, but I think that it covers the basic bug-fixing process sufficiently well as to apply to all organizations, and thus should be the default

Comments

bugzilla workflow

[jdragojevic]

So we've only been using Bugzilla for about a year now at PCF. As as QA I completely prefer it to other bug systems I've used in the past. However I have to disagree with the proposed changes

Re: bugzilla workflow

[avatraxiom]

You will still know that a bug is new from the subject of the email. The "New: " word on the subject line of the email has nothing to do with the status of the bug.

When a developer is assigned a bug, what would make you think that they wouldn't be aware of it or accept it? Bugzilla sends emails to asssignees, and you can see that it sent an email to that engineer. An engineer who is not willing to fix a bug can reset the assignee to the default, or we may make it possible to have bugs assigned to Nobody.

-Max