Summary: | change the label from NEW to CONFIRMED | ||
---|---|---|---|
Product: | [Websites] bugs.kde.org | Reporter: | Maciej Pilichowski <bluedzins> |
Component: | templates | Assignee: | Ingo Malchow <imalchow> |
Status: | RESOLVED FIXED | ||
Severity: | wishlist | CC: | kde, myriam, toma |
Priority: | HI | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | All | ||
Latest Commit: | Version Fixed In: |
Description
Maciej Pilichowski
2009-06-05 10:40:41 UTC
*** Bug 246881 has been marked as a duplicate of this bug. *** Bumb. I still think this would be a really great change, as it is misleading for everybody. I would also prefer the status CONFIRMED over NEW. But it would IMHO be even better if the database could be converted to the new Bugzilla 4 status workflow which is a lot easier to understand and much less of a hassle to maintain. Not only does it have a status CONFIRMED instead of NEW, there is also no confusion anymore about the difference between RESOLVED and CLOSED and it also doesn't provide any meaningless combinations such as RESOLVED LATER or NEEDSINFO FIXED anymore. I know that a conversion is connected with a decent amount of effort, but it would be worth it. BTW Here is an overview of the new bug status workflow: http://www.bugzilla.org/docs/4.0/en/html/lifecycle.html NEW has now been renamed to CONFIRMED. |