Bug #14815 Updated: quick way to mark a bug bogus and give common reasons
| From: | mrobinso@php.net | Date: | Fri, 25 Jan 2002 18:03:21 +0000 |
| Subject: | Bug #14815 Updated: quick way to mark a bug bogus and give common reasons | ||
| References: | 1 | Groups: | php.mirrors |
| Request: | Send a blank email to php-mirrors+get-8310@lists.php.net to get a copy of this message | ||
ID: 14815
Updated by: mrobinso
Reported By: jimw@apache.org
Status: Open
Bug Type: Website problem
Operating System: linux
PHP Version: 4.1.1
New Comment:
A drop down list or radio buttons with a list of common
remarks would be helpful:
1. Fixed in CVS, thanks for your report...
2. Please provide a backtrace to this report. See ... for
instructions...
3. Old version, please upgrade and reopen if problem persists...
4. Please ask support-related questions on the php-general list...
5. No feedback -> closing.
6. Not a bug...
7. Not a proper bug report, please read the dos-and-donts...
There's probably others than can be used as well.
Makes the bug db cleanup a little quicker and adds
some consistency/friendliness to common comments.
Previous Comments:
------------------------------------------------------------------------
[2002-01-02 20:37:25] jimw@apache.org
sometimes the marking of a bug as "bogus" can be a bit jarring for the
reporter. it would be nice to have a quick way to mark a bug bogus and
use a canned response about the particularly flavor of bogosity it
exhibited. (and "bogus" should probably be named "not a bug".)
------------------------------------------------------------------------
Edit this bug report at http://bugs.php.net/?id=14815&edit=1