Bug 190587

Summary:	Issue resolved should provide more states to indicate how and if an issue was resolved
Product:	Services	Reporter:	Marcus von Appen <mva>
Component:	Bug Tracker	Assignee:	Bugmeister <bugmeister>
Status:	Closed FIXED
Severity:	Affects Only Me	CC:	berg2839, feld, kwm
Priority:	---
Version:	unspecified
Hardware:	Any
OS:	Any

Description Marcus von Appen freebsd_committer

2014-06-03 19:10:36 UTC

Right now we just provide

* FIXED
* As Intended
* DUPLICATE

as status refinements for "Issue Resolved".

This does not cover things like 

* being unable to reproduce (-> Can't Reproduce)
* missing feedback (-> No Feedback)
* will never be fixed (-> Won't Fix)

Those additional information would be highly appreciated.

Comment 1 Eitan Adler freebsd_committer

2014-06-03 23:01:33 UTC

*** Bug 190583 has been marked as a duplicate of this bug. ***

Comment 2 Eitan Adler freebsd_committer

2014-06-04 05:47:41 UTC

so. we won't do "Won't Fix" since the state needs to reflect the reason that it won't be fixed.

"Not Enough Information" ("No Feedback") is fine.
"Unable to Reproduce" is fine.


If these are sufficient mark this bug "loop closed"; else re-open with additional content.

Comment 3 Marcus von Appen freebsd_committer

2014-06-04 05:57:24 UTC

Those are sufficient at the moment. Thanks!

Comment 4 Andrew Berg 2014-06-05 08:19:59 UTC

Bug 190583 is marked as a dupe of this, but the current options don't cover invalid bugs (e.g., bugs that should be reported elsewhere).

Comment 5 Eitan Adler freebsd_committer

2014-06-05 15:04:08 UTC

reopen due to comment below

Comment 6 Koop Mast freebsd_committer

2014-06-05 19:26:17 UTC

Can we also have a "superseded by" state? (yes typos wheee)
Duplicated comes close but not quite..

see the following bugs are example:
Update link-grammer to
5.0.3 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188642
5.0.4 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188738
5.0.6 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188840

The 5.0.3 and 5.0.4 should be able to be marked superseded by the 5.0.6 update.

Comment 7 Eitan Adler freebsd_committer

2014-06-06 02:29:33 UTC

I think "overcome by events" along with adding a "see also" is likely correct.  Adding a new "enter a bug number here" resolution is actually quite difficult.

Comment 8 Eitan Adler freebsd_committer

2014-06-07 07:43:23 UTC

I added "Report to Upstream".  for additional states its likely better to open a new bug and add this one as a see also.