126211 - Make state transitions more customizable

Status: RESOLVED DUPLICATE of bug 101179

(Bugzilla :: Creating/Changing Bugs, enhancement)

Description

[Chris Hubbard]

In our implmentation of Bugzilla, we added AssnStatus and QAStatus so that we 
(developers & management) and track the status of the bug during the ASSIGNED 
bug_status and during the RESOLVED, FIXED bug_status, resolution.  

AssnStatus included states for "In progress", "Integration test", and "3rd 
party problem" (which stated that the bug is halted while waiting on a fix from 
a dependent component).

QAStatus includes states for which testing group is currently testing the bug, 
QA Accepted, and QA Rejected.

We changed the "Verify" knob to change the QAStatus to "QA Accepted" along with 
the bug_status to Verified.

We also added a "Reject" knob to change the QAStatus to "QA Rejected" along 
with the bug_status to "Assigned" (instead of New as reopen does).

We are trying to keep our codebase as close to that of the main line Bugzilla 
codebase and are willing to work on a more customizable state transition 
frontend so that users of Bugzilla don't have to make as many changes as we 
have had to do.

Comment 1

[Matthew Tuck [:CodeMachine]]

I welcome any offer of help.  I was intending to do this for 2.18, but if anyone
beats me to it, all well and good.

However, we do have some plans as to how this should be done and rules as to how
new code should work that you might like to look at.  If you wish to work on
this:

- Please see the discussion on the duplicate bug.
- Familiarise yourself with the Template Toolkit that Bugzilla is transitioning
to.
- Familiarise yourself with how taint mode works.
- Familiarise yourself with editresolutions.cgi and admineditor.pl on the
CUST_RES_BRANCH.  I expect editstatuses.cgi and editstatustransitions.cgi will
work in this way.
- Also maybe familiarise yourself with other parts of this branch which
implements customised resolutions (bug #94534).

I might support substates for open statuses (ie resolution is a substate for
non-open ones), but I don't see there being a second substate on top of status
and resolution.

I expect you can just use status for all this, and we might customise the
transitions to only be possible for certain resolutions.

*** This bug has been marked as a duplicate of 101179 ***