Bug #13311 Updated: status, severity, and category should be distinct in bug database
| From: | jimw@php.net | Date: | Sat, 20 Oct 2001 06:20:44 +0000 |
| Subject: | Bug #13311 Updated: status, severity, and category should be distinct in bug database | ||
| References: | 1 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-7119@lists.php.net to get a copy of this message | ||
ID: 13311
Updated by: jimw
Reported By: jeroen@php.net
Old Summary: Bug categorization wrong
Status: Open
Bug Type: Website problem
Operating System: http
PHP Version: 4.0CVS-2001-09-14
New Comment:
just a new summary.
Previous Comments:
------------------------------------------------------------------------
[2001-09-14 19:58:49] jeroen@php.net
The categorization of bugs is a bit strange. A more natural and IMO better solution would be:
- status (open, closed, assigned, ...)
- Type (feature request, cricial bug, performance problem, crash, security problem, Bogus,
Documentation problem, ...)
- Category (arrays-related, IMAP, website problem, ...)
Currently there cannot be a closed critical bug, (would be interesting for historical purposes,
which critical bugs were in 403?), no categorization of feature requests, etc etc.
I would have liked to classify this bug as website problem: feature-request, but since category and
type are mixed up, I can't...
------------------------------------------------------------------------
Edit this bug report at http://bugs.php.net/?id=13311&edit=1