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

go to bug id or search bugs for

Request #62403 limit duplicate by adding a instant search in the bug report's form
Submitted: 2012-06-24 11:31 UTC Modified: 2015-01-03 10:43 UTC
From: perdrisat at gmail dot com Assigned: jacob (profile)
Status: Closed Package: Website problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
 [2012-06-24 11:31 UTC] perdrisat at gmail dot com 
Description:
------------
Apparently half of the bugs are duplicate or not a bug...

I think this can partially solve by improving the bug report system. We need to search and display similar bugs when the user try to make a new one.

One of the best example is certainly http://stackoverflow.com/questions/ask

Now we can of making a search after the submit... when the user already spend time to write is report. Also the page is not very clear because their is no title like "similar bug report, please avoid duplicate"

Expected result:
----------------
- (user) got to https://bugs.php.net/report.php
- (user) write the title of the bug report
- (system) Do a (ajax) search and show a short list of similar bug report (possible duplicate) right under the title.
- (user) look if is bug is a new one
- (user) submit if he think it's a new or cancel if it's a duplicate.

Actual result:
--------------
- (user) got to https://bugs.php.net/report.php
- (user) write the title of the bug report
- (user) write the bug report
- (user) submit

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2013-03-01 10:40 UTC] kalle@php.net 
Didn't we have a similar system like that implemented in the old bugsweb? I remember that when you were about to submit a report and it was similar to one or more you were presented with 3 or more similar reports and you had to re-confirm that it was not an already reported bug or declined feature.
 [2013-03-24 20:34 UTC] tyrael@php.net 
we do have one, after you submit a bug report you will be presented with the 
similar reports and you have to comfirm, that your issue isn't there.
except if you are a logged in developer, then you won't have to confirm.
 [2013-03-25 09:01 UTC] perdrisat at gmail dot com 
So what would be better is having duplication search before submitting. Because it can be very frustrated if you spend half an hour to create a good bug report just to find than it's a duplicate. In this case if you bug is slightly different you will have a to much incentive to publish it anyway instead of adding more information of the other one.
 [2013-03-25 12:18 UTC] danielc@php.net 
Perdrisat:  People should search the bug database before submitting a report.

In fact, to report a bug, people go to https://bugs.php.net/, where the following text is the first bullet in the list of things to have done before opening a new bug:

"Used the form above or our advanced search page to make sure nobody has reported the bug already."
 [2015-01-03 10:43 UTC] jacob@php.net
-Status: Open +Status: Closed -Assigned To: +Assigned To: jacob
 [2015-01-03 10:43 UTC] jacob@php.net 
Closed due to inactivity.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Fri May 17 12:01:32 2024 UTC