php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #13311 status, severity, and category should be distinct in bug database
Submitted: 2001-09-14 19:58 UTC Modified: 2003-08-10 17:52 UTC
Votes:1
Avg. Score:5.0 ± 0.0
Reproduced:0 of 0 (0.0%)
From: jeroen@php.net Assigned:
Status: Closed Package: Website problem
PHP Version: 4.0CVS-2001-09-14 OS: *
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: jeroen@php.net
New email:
PHP Version: OS:

 

 [2001-09-14 19:58 UTC] 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...

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-10-20 02:20 UTC] jimw@php.net
just a new summary.
 [2002-11-13 07:42 UTC] nicos@php.net
Too old.
 [2002-11-13 10:23 UTC] goba@php.net
Hey these are reminders for Jim, or anyone else who will participate in developing the new bug system :O
 [2003-08-10 17:52 UTC] helly@php.net
It works fine for us and is accepted by our users as it currently is.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sun Dec 22 01:01:30 2024 UTC