Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 367944 - Bug fields doc doesn't describe severity any more
Summary: Bug fields doc doesn't describe severity any more
Status: RESOLVED WONTFIX
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Bugzilla (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-05 08:27 EST by Markus Keller CLA
Modified: 2021-12-20 10:53 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2012-01-05 08:27:34 EST
When I click the "Importance" label in a bug, the doc page https://bugs.eclipse.org/bugs/page.cgi?id=fields.html#importance doesn't explain the severities any more:

- anchor #importance doesn't exist
- Severity just says:
    How severe the bug is, or whether it's an enhancement.

In 3.6, the severity field was fully described here:
https://landfill.bugzilla.org/bugzilla-3.6-branch/page.cgi?id=fields.html#importance

Furthermore, the Open Bugs statuses are wrong in the current doc (we still use NEW and ASSIGNED).
Comment 1 Dani Megert CLA 2012-04-18 03:07:40 EDT
Can this please get fixed?
Comment 2 Dani Megert CLA 2012-06-05 10:10:37 EDT
Ping!
Comment 3 Markus Keller CLA 2012-07-02 12:34:35 EDT
Ping.
Comment 4 Dani Megert CLA 2013-01-22 11:58:46 EST
Ping ;-)
Comment 5 Markus Keller CLA 2013-02-22 13:38:32 EST
Copying the missing information here, so that I have one step less to look it up ...

Severity
This field describes the impact of a bug.

blocker 	Blocks development and/or testing work
critical 	crashes, loss of data, severe memory leak
major 		major loss of function
normal 	regular issue, some loss of functionality under specific circumstances
minor 	minor loss of function, or other problem where easy workaround is present
trivial 	cosmetic problem like misspelled words or misaligned text
enhancement 	Request for enhancement
Comment 6 Denis Roy CLA 2013-03-14 11:33:38 EDT
It seems the Importance label and severity descriptions were removed in the 4.2 version:

https://landfill.bugzilla.org/bugzilla-4.2-branch/page.cgi?id=fields.html#importance


I wonder why...
Comment 7 Denis Roy CLA 2013-03-14 11:48:16 EDT
Seems the text was moved to another page, but seemingly removed altogether:

https://bugzilla.mozilla.org/show_bug.cgi?id=529201#c13
Comment 8 Dani Megert CLA 2013-03-21 06:38:30 EDT
Any chance to fix this on our end? Users often set a wrong severity because they don't know what they mean, or change the priority field, even if they should not do so. In Eclipse we used the definitions from
https://landfill.bugzilla.org/bugzilla-3.6-branch/page.cgi?id=fields.html
for many years and they still hold.
Comment 9 Dani Megert CLA 2013-06-17 04:56:10 EDT
Please...
Comment 10 Dani Megert CLA 2014-04-22 04:56:24 EDT
(In reply to Dani Megert from comment #9)
> Please...

One last try ;-)

If you think you'll never do it, then please just close the bug as WONTFIX.
Comment 11 Lars Vogel CLA 2014-04-22 05:12:08 EDT
(In reply to Dani Megert from comment #10)
> (In reply to Dani Megert from comment #9)
> > Please...
> 
> One last try ;-)
> 
> If you think you'll never do it, then please just close the bug as WONTFIX.

I adjusted the wiki page: https://wiki.eclipse.org/Bug_Reporting_FAQ#What_is_the_difference_between_the_Bug_priorities.3F

Given the age of this bug, maybe we should close it as WONTFIX? Even Markus and Danis frequent pings did not help in getting this solved.
Comment 12 Denis Roy CLA 2014-04-24 09:09:07 EDT
Why WONTFIX?  I'll fix this at some point. Or is there an expiry date on bugs?

I do thing the "major" importance is wildly overblown though.
Comment 13 Eclipse Genie CLA 2016-04-14 17:49:32 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 15 Dani Megert CLA 2016-04-15 04:28:15 EDT
(In reply to Denis Roy from comment #12)
> Why WONTFIX?  I'll fix this at some point. Or is there an expiry date on
> bugs?
> 
> I do thing the "major" importance is wildly overblown though.

That's true.
Comment 16 Eclipse Genie CLA 2018-04-06 12:03:04 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 17 Dani Megert CLA 2018-04-06 12:17:42 EDT
(In reply to Eclipse Genie from comment #16)
> This bug hasn't had any activity in quite some time. Maybe the problem got
> resolved, was a duplicate of something else, or became less pressing for
> some reason - or maybe it's still relevant but just hasn't been looked at
> yet.
> 
> If you have further information on the current state of the bug, please add
> it. The information can be, for example, that the problem still occurs, that
> you still want the feature, that more information is needed, or that the bug
> is (for whatever reason) no longer relevant.
> 
> --
> The automated Eclipse Genie.

Not fixed yet.
Comment 18 Eclipse Genie CLA 2020-03-27 12:45:01 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 19 Denis Roy CLA 2021-12-20 10:53:52 EST
We won't be investing any resources into improving Bugzilla, as we encourage projects to use GitHub and Eclipse GitLab (https://gitlab.eclipse.org).

Please see: Shutdown this bugzilla instance.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=577151