Today, Bugzilla handles bugs very satisfactory. A bug has a state: new, assigned, resolved, verified. What we would like is to be able to define states independently (any number and names), and some simple rules on how state changes are allowed (who can do it, a-->b, b-->c, but not a-->c). Still better: More advanced rules such that two parties must approve before a state change. I should think that Bugzilla is capable of such enhancements, but states and such are so tangled into the perl code that I cannot do it myself. Any chance of such enhancements?
I guess all this can be called "workflow" definition?
Reassigning bugs that I'm not actively working on to the default component owner in order to try to make some sanity out of my personal buglist. This doesn't mean the bug isn't being dealt with, just that I'm not the one doing it. If you are dealing with this bug, please assign it to yourself.
Assignee: justdave → general
QA Contact: mattyt-bugzilla → default-qa
This bug needs to be split into two bugs: 1. Stop referring to bugs and generalize them into 'tasks' or 'issues' or whatever. 2. Generalize the resolution scheme Item 2 is the main scope of comment #0, so I'm renaming this bug accordingly. Reporter/s, please open a separate bug about issue 1 or consult the related bug 75172.
Summary: Generalizing Bugzilla into a "task tracking system" → Generalize resolution scheme into state schemes with transition rules
(In reply to Eyal Rozenberg from comment #3) > 1. Stop referring to bugs and generalize them into 'tasks' or 'issues' or > whatever. This has nothing to do with this bug. Comment 0 is about custom bug statuses and workflow. > 2. Generalize the resolution scheme This bug is about bug statuses, not resolutions. Bugzilla supports both points for ages now -> WFM.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.