We will also have the chance to do other customizations, for
instance to
the workflow (as an example, we'll be able to solve this
NEW/ACCEPTED/STARTED problem by having a dedicated ACCEPTED issue
status).
+1 for adding an ACCEPTED status different from a STARTED status.
While we are at the topic of issue status I would also suggest to
replace WORKSFORME with NOT_REPRODUCABLE. Also split DUPLICATE into
DUPLICATE_ISSUE and DUPLICATE_ROOTCAUSE because very often fixes non-
trivial root causes solve issues that are quite different from the
reported issue.
One thing I'd be interested in getting feedback for is the following
question: Do we need the issue types ENHANCEMENT and PATCH?
ENHANCEMENT
isn't really different from FEATURE (at least in practice, though in
theory you could define them differently),
Refactoring code, performance improvements, supporting obsolete and
deprecated but still used stuff, etc. do neither deserve a
classification as DEFECT nor as FEATURE. Such changes should still be
tracked so one can read about their background, about design
considerations, limitations, testing hints etc. ENHANCEMENT is a good
name for such issues with such a status.
PATCH, then, could effectively be a TASK with an attachment of type
"Patch".
In my opinion PATCH should never have been an issue type. A patch is a
change for either fixing a DEFECT, for providing an ENHANCEMENT or
implementing a FEATURE, but in itself the status was just confusing.
Having an extra patch flag would be better, also for the automatic
queries Bernd mentioned. An extra flag can also be enabled when non-
attached but inline patches are concerned or a flag could be disabled
when it is not considered to solve the reported issue.
---
Herbert Duerr
[email protected]
Registered Office: Sun Microsystems GmbH
Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Commercial register of the Local Court of Munich: HRB 161028
Managing Directors: Thomas Schroeder, Wolfgang Engels
Chairman of the Supervisory Board: Martin Haering
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
