php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #14815 quick way to mark a bug bogus and give common reasons
Submitted: 2002-01-02 20:37 UTC Modified: 2002-02-01 15:26 UTC
From: jimw at apache dot org Assigned:
Status: Closed Package: Website problem
PHP Version: 4.1.1 OS: linux
Private report: No CVE-ID: None
View Developer Edit
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: jimw at apache dot org
New email:
PHP Version: OS:

 

 [2002-01-02 20:37 UTC] jimw at apache dot 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".)

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-01-25 13:03 UTC] mrobinso@php.net 
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.
 [2002-02-01 15:26 UTC] jimw@php.net 
added.
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Sun May 11 08:01:28 2025 UTC