BugClosedNoFeedback
From AbiWiki
(Difference between revisions)
m (Reverted edits by Newspopularity (Talk) to last revision by Maintenance script) |
|||
| Line 1: | Line 1: | ||
| - | + | === Bugzilla: Bug Closed -- No Feedback === | |
| - | === Bugzilla: Bug Closed | + | |
If developers have asked for additional information in a Bug, and the reporter (or someone else) has not provided it within 2 weeks, the Bug will be closed as INVALID. | If developers have asked for additional information in a Bug, and the reporter (or someone else) has not provided it within 2 weeks, the Bug will be closed as INVALID. | ||
| - | Lack of response in a Bug usually means that the reporter no longer cares about the problem - and there | + | Lack of response in a Bug usually means that the reporter no longer cares about the problem - and there's little point in bloating the Bug database with such Bugs. |
If the reporter was simply prevented from adding the information in a timely manner, no harm is done; simply add the information to the Bug, and reopen it. Then the developers will look at it again. | If the reporter was simply prevented from adding the information in a timely manner, no harm is done; simply add the information to the Bug, and reopen it. Then the developers will look at it again. | ||
| - | See also the [[ | + | See also the [[FAQ Bug Policy|Bug Policy]]. |
| - | + | [[Category:Bug Tracking]] | |
| - | [[Category: | + | |
Current revision as of 19:39, 26 December 2010
Bugzilla: Bug Closed -- No Feedback
If developers have asked for additional information in a Bug, and the reporter (or someone else) has not provided it within 2 weeks, the Bug will be closed as INVALID.
Lack of response in a Bug usually means that the reporter no longer cares about the problem - and there's little point in bloating the Bug database with such Bugs.
If the reporter was simply prevented from adding the information in a timely manner, no harm is done; simply add the information to the Bug, and reopen it. Then the developers will look at it again.
See also the Bug Policy.
