Bug 94106

Summary:	not all resolutions are explained
Product:	Gentoo Infrastructure	Reporter:	Alin Năstac (RETIRED) <mrness>
Component:	Bugzilla	Assignee:	Bugzilla Admins <bugzilla>
Status:	RESOLVED FIXED
Severity:	minor	CC:	ago, ifreecarve, kentnl, toralf, vapier
Priority:	High	Keywords:	PATCH
Version:	unspecified
Hardware:	All
OS:	Other
URL:	http://bugs.gentoo.org/page.cgi?id=fields.html#resolution
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	0001-resolutions-document-all-the-ones-we-use.patch

Description Alin Năstac (RETIRED) gentoo-dev

2005-05-26 12:25:24 UTC

the new bugzilla has only some resolutions explained (FIXED, INVALID, WONTFIX, DUPLICATE, WORKSFORME and MOVED), leaving the rest of them up to our imagination.

the old bugzilla had all resolutions explained

Comment 1 Jeffrey Forman (RETIRED) gentoo-dev

2005-07-18 12:01:08 UTC

i am unable to find the old copy of the resolution statuses. i will try to hack
something up on the next upgrade.

Comment 2 Jakub Moc (RETIRED) gentoo-dev

2005-10-01 07:20:59 UTC

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

Comment 3 Jakub Moc (RETIRED) gentoo-dev

2006-07-12 05:46:35 UTC

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

Comment 4 Kent Fredric (IRC: kent\n) (RETIRED) gentoo-dev

2014-07-01 19:55:27 UTC

In bug #515970 , a user was confused by the definition of the "RESOLVED UPSTREAM" status.

Or its even possible "RESOLVED UPSTREAM" was inappropriate because by my observation, no corresponding bug was filed upstream.

And upon observing the "status" fields list, there is no definition of that resolution term.

I personally expected it to be a wrong resolution, because the bug was neither resolved, nor reported upstream.

However, further digging revealed, that contrary to my expectation, that "UPSTREAM" conveys "Please file this bug upstream", not "This problem is fixed upstream", and the distinction aught to be made clearer, and in an appropriate place.

( Ideally a comment telling users what this means and what they should do next would accompany a resolution, but having the status documented in the list of available statuses would be a good start, and is the primary motive for this bug. )

NB. It is very sad that this bug has been sitting here rotting unfixed for ... 9 years.

Comment 5 Kent Fredric (IRC: kent\n) (RETIRED) gentoo-dev

2014-07-01 20:07:18 UTC

Reopening and resetting assignee, because 

a) resolved later  is no longer a valid resolution
b) the assignee is retired
c) this is still a bug

Comment 6 SpanKY gentoo-dev

2015-05-23 05:19:10 UTC

Created attachment 403800 [details, diff]
0001-resolutions-document-all-the-ones-we-use.patch

Comment 7 SpanKY gentoo-dev

2015-05-24 06:19:04 UTC

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

Comment 8 SpanKY gentoo-dev

2016-04-02 20:56:40 UTC

should be live now:
https://gitweb.gentoo.org/proj/gentoo-bugzilla.git/commit/?id=d86e408d4a54d30bcbae224f9d35e413657e6b04
https://bugs.gentoo.org/page.cgi?id=fields.html#bug_status