ubuntu-bugcontrol team mailing list archive

[Micah Gersten <micahg@xxxxxxxxxx>]

+1 and this applies to more than just Server bugs.

On July 20, 2015 10:36:33 AM CDT, Thomas Ward <teward@xxxxxxxxxxx> wrote:
>While I usually don't bother to comment on these, should we re-evaluate
>the "Mark a report which has no debuggable information as invalid"
>approach?  Given some server bugs of which users just need to include
>additional information, perhaps we should expand this to say instead
>"The report does not contain adequate information to determine whether
>or not it is a bug, or the reporter has not attached requested
>information, even if the issue is resolved for the reporter" or
>similar.
>
>At some level, a bug just missing a couple bits of information that
>could be provided by the reporter may just be "Incomplete" rather than
>"Invalid".  At some point, then, it should either Expire or go Invalid
>if nobody's giving additional information, but initially, it sounds
>more
>like this would be an "Incomplete" case, rather than "Invalid".
>
>
>Thomas
>
>
>
>-------- Forwarded Message --------
>Subject: 	[Ubuntu Wiki] Update of "Bugs/Bug statuses" by penalvch
>Date: 	Sun, 19 Jul 2015 16:01:29 -0000
>From: 	Ubuntu Wiki <noreply@xxxxxxxxxx>
>To: 	Ubuntu Wiki <noreply@xxxxxxxxxx>
>
>
>
>Dear Wiki user,
>
>You have subscribed to a wiki page or wiki category on "Ubuntu Wiki"
>for change notification.
>
>The "Bugs/Bug statuses" page has been changed by penalvch:
>http://wiki.ubuntu.com/Bugs/Bug%20statuses?action=diff&rev1=75&rev2=76
>
>Comment:
>Due to LP#1178982 c#38 and others, clarified Status Invalid.
>
>* This status is considered an experiment, and will be closely
>monitored.
>  
>   * '''Invalid''':
>+   * This status means the report is closed, and no further triaging
>or development will continue towards it.
>+   * This status should be used when:
>-   * This status should be used when the report does not contain
>adequate information to determine whether or not it is a bug even if it
>is resolved for the reporter.
>+    * The report does not contain adequate information to determine
>whether or not it is a bug, even if it is resolved for the reporter.
>-   * This should also be used if the reported problem is not a bug at
>all. For example, user's lack of knowledge on how something works,
>hardware failure, or fixed after updating a buggy, and outdated BIOS.
>+    * The reported problem is not a bug at all. For example, the
>reporter's lack of knowledge on how something works, hardware failure,
>or fixed after updating a buggy, and outdated BIOS.
>* It should be used conservatively as reports marked as Invalid no
>longer show up in default searches.
>    * Be sure to triple-check a report before you invalidate it.
>