From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4 Description of problem: Hi, I would like to see bugs being auto-closed which are in "NEEDINFO" status and the ticket starter hasn't replied to it within 3 weeks. imho it's a waste of time for us all. The ticket should be closed with the following texts or something like that: "This report is being automatically closed after 3 weeks because the required information to resolve the alleged issue has not been provided. If you have the necessary information, please feel to reopen this report and provide us the details. Thank you!" Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: n/a Additional info:
Just a note that this is being requested for Fedora Triaging. Thanks
Noticed the discussion about this on the list at http://www.redhat.com/archives/fedora-triage-list/2005-September/msg00000.html Just wondering if this is going to be implemented in Bugzilla?
I think this is a fine idea. The debate internally here has always been how long is a good amount of time. If the Fedora triage community can agree on specific amount of time, a canned response to add to the closed bug and the proper resolution, I do not mind implementing this for the Fedora Core product only for now. Other products can come into play later.
All of the requested information has already been provided in the original report. Time: 3 weeks Stock Response: ""This report is being automatically closed after 3 weeks because the required information to resolve the alleged issue has not been provided by the user. If you have the necessary information, please feel to reopen this report and provide us the details. Thank you"
If the original poster of a bug has "lost interest" and doesn't supply the "NEEDINFO" info, but I am encountering the same bug, how should I proceed? If I, not being the original reporter, supply "info" will it cancel the pending closure, or will info only from the original poster do that? If the bug is closed, should I then file a duplicate with me as the reporter?
Three weeks is too short. People go on holiday, or are sick, for three weeks. I say, make it five at least. Some people are very good in filing bugs, and hence have very long lists of bugs in their collection. If a bug falls off the list due to this, they might not notice, and their work in filing the issue is wasted.
(In reply to comment #5) > If the original poster of a bug has "lost interest" and doesn't supply the > "NEEDINFO" info, but I am encountering the same bug, how should I proceed? > If I, not being the original reporter, supply "info" will it cancel the > pending closure, or will info only from the original poster do that? If > the bug is closed, should I then file a duplicate with me as the reporter? You can change the status or file a new bug report referencing the one being closed.
(In reply to comment #6) > Three weeks is too short. People go on holiday, or are sick, for three weeks. > I say, make it five at least. Some people are very good in filing bugs, and > hence have very long lists of bugs in their collection. If a bug falls off the > list due to this, they might not notice, and their work in filing the issue is > wasted. When bugs are closed the reporter as well as everyone CC'ed on the bug report will get a notification. The reporter can very well reopen the bug after the person returns back from vacation. There is no point in cluttering bugzilla with reports which have no progress.
Two years later, I've found this bug :). I am going to be at FUDcon this weekend, where a policy will be decided. What's the level of effort to get this implemented?
We've decided that we don't want this. Bugs in NEEDINFO will be subject to manual review for Fedora.