Bug importances
Ubuntu uses the following guidelines for assigning importance. The importance of the bug signifies the priority that it should be given by people fixing bugs.
In order to set the Importance field in [:Malone], you need to be a member of [:UbuntuQA] either through direct membership or because of your membership in another team. The importance of the bug should be set as soon as possible.
Undecided: the default importance for new bugs. It means that there is not sufficient information to determine its importance.
Wishlist: a request to add a new feature to one of the programs in Ubuntu.
- These aren't always bugs, but can be ideas for new features which do not yet exist.
If it is non-trivial to implement, it should rather be written as a feature specification, see FeatureSpecifications
Low: Bugs which affect functionality, but to a lesser extent than most bugs, examples are:
- Ones that can be easily worked around
- Ones that affect unusual configurations or uncommon hardware
Medium: most bugs are of medium importance, examples are:
- A bug that has a moderate impact on a core application.
- A bug that has a severe impact on a non-core application.
- A problem with a non-essential hardware component (network card, camera, webcam, music player, sound card, power management feature, printer, etc.)
High: A bug which fulfills one of the following criteria:
- Has a severe impact on a small portion of Ubuntu users (estimated)
- Makes a default Ubuntu installation generally unusable for some users
- For example, if the system fails to boot, or X fails to start, on a certain make and model of computer
- A problem with an essential hardware component (disk controller, laptop built-in wireless, video card, keyboard, mouse)
- Has a moderate impact on a large portion of Ubuntu users (estimated)
Critical: A bug which has a severe impact on a large portion of Ubuntu users