Bug importances
|
This page is part of the
Undecided
No one has set priority yet.
We don't know what importance should it have yet.
Wishlist
Is an idea for a new feature.
Is a requests to package software for Ubuntu.
Affect an experimental extension or non-essential feature.
Would only be fixed on a best-effort or outside-contribution basis.
Is non-trivial to implement (it should rather be written as a feature specification).
Low
Has an easy work-around.
Affects unusual end-user set up.
Affects a non-essential aspect of the application.
Has a moderate impact on a non-core application.
Is a cosmetic or usability issue that doesn't limit the functionality of a non-core application.
Is a non-ideal default configuration.
Medium
Most bugs fit this importance.
Has a moderate impact on a core application.
Has a severe impact on a non-core application.
Impacts accessibility of a non-core application.
Is a usability issue that doesn't limit the functionality of a core application.
Affects a non-essential hardware component (removable network card, camera, web-cam, music player, sound card, power management feature, printer...).
High
Is estimated to have severe impact on an small portion of Ubuntu users.
Makes a default Ubuntu installation unusable for some users.
Affects an essential hardware component (disk controller, built-in networking, video card, keyboard, mouse).
Is estimated to have a moderate impact on a large portion of Ubuntu users.
Prevents the application (or a dependent one) from functioning correctly at all.
Renders essential features or functionality of the application (or a dependent one) broken.
Impacts accessibility of a core application.
Critical
Has a severe impact on a large portion of Ubuntu users.
Causes data corruption.
Crashes the entire operating system.
Renders the system temporarily or permanently unusable.
Severely affects applications beyond the one that causes the flaw.
This importance can be set by:
Asking someone in #ubuntu-bugs channel at FreeNode to set it for you to a specific priority.
Becoming a member of Ubuntu Bug Control.
Footnote: |
|
"core": |
A core package can be identified as being part of a task in the apt-cache headers. You can see the apt-cache headers by running apt-cache show [package] in a terminal, and looking at the "Task: " field in the output. |
"non-core": |
A non-core package can be identified as a package that is not part of a task, and is not in 'main'. You can see the apt-cache headers by running apt-cache show [package] in a terminal, and looking at the "Task: " field in the output. |