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

go to bug id or search bugs for

Bug #34313 bugs.php.net keeps marking bugs as "No Feedback" even when there has been
Submitted: 2005-08-31 02:45 UTC Modified: 2005-08-31 10:49 UTC
From: php dot net at nanonanonano dot net Assigned:
Status: Not a bug Package: Website problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
View Developer Edit
 [2005-08-31 02:45 UTC] php dot net at nanonanonano dot net 
Description:
------------
Several times, a bug in which I am interested has been marked as "No Feedback" even though comments have been posted confirming that the bug is still present in more recent snapshots. It seems that only feedback from the original poster is able change the status of the bug from "Feedback" to "Open".

Reproduce code:
---------------
See full history of http://bugs.php.net/bug.php?id=24485 (including the cycles of "try this snapshot"/"not fixed" that have been deleted from the comments)

Expected result:
----------------
Either other interested users should be able to re-open bugs that are on "feedback" or the automated process that moves bugs from "feedback" to "no feedback" should check to see if a comment has been left since the request for feedback was made. If a comment has been made then human interaction should be required.

Actual result:
--------------
Bugs are being automatically closed even though they have not been fixed.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-08-31 09:06 UTC] derick@php.net 
Comments by other people not being the original subscriber of a bug do not count as "Feedback". This is a feature.
 [2005-08-31 09:17 UTC] php dot net at nanonanonano dot net 
I can understand this perhaps being a good comment-spam preventing feature, but it doesn't get around the problem of bugs being closed because of lack of feedback even though they are identified as being still open. 

If I were to create a new bug on the same issue so that I could provide feedback in lieu of the original submitter being responsive, then that new bug report would be closed as a duplicate... so it becomes a catch-22 situation -- there is no way of actually reporting that a problem still exists once a bug is marked as No Feedback.

As per my original post on this issue, if some human interaction were required if there were comments post-dating the request for feedback, then this wouldn't be such a problem.
 [2005-08-31 10:49 UTC] sniper@php.net 
If you open a new report and there's already one about same issue but with 'No feedback', your report will not be duplicate.
 [2015-05-24 03:12 UTC] danielklein at airpost dot net 
I have just submitted a bug report about this bug (not a duplicate!) The bug is at https://bugs.php.net/bug.php?id=69697 where I mention the workaround I used to get my bug looked at again.
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Tue Jul 08 20:01:34 2025 UTC