P1 |
doesn't work
no workarround exists | Product feature does not work, no workaround exists |
| data loss | User's data are corrupted or lost |
| crash or deadlock | Reproducible, unavoidable crash or deadlock |
| regression | Regression in functionality or performance |
| memory leak | Huge memory leak |
| performance |
Very bad UI responsiveness making the feature unusable
Scalability problem making the feature unusable in an usual scenario
|
| accessibility |
Crash or exception caused by cooperation of NetBeans IDE with Assistive Technology (problem caused by NetBeans IDE in chain Orca->Access bridge->Java VM->NetBeans IDE)
Any functionality available by mouse is not reachable by keyboard
Opened window doesn't gain the focus directly and there is no way to reach it by keyboard (invoked window hides, minimizes or stays on background immediately with no possibility to focus it)
Component 'eats' focus (doesn't release it) - cannot switch to another component by keyboard
Font, Color or Sound are being used as the only cue to the user (e.g red text as a warning, beep as an indication of wrong selection)
Not implemented Accessible API
Neither Accessible Name nor Accessible Description is set
|
| internationalization |
When user running in other supported locale (whether using localized
product or not), runs into any of the situations described in this P1
section, that don't happen when they run in en locale
User running in other locale uses or inputs characters of that locale
in their code or apps, and its legal in the java language or other api/spec
to do so to do so, and any of the situations described in this P1 section
happens that don't happen when they run in en locale
|
| others |
Blocks another developer's progress, no workaround exists
Incorrect text or graphics with legal implications
|
|
|
P2 |
doesn't work
workarround exists | Product feature doesn't work, a workaround may exist but it's difficult to use or impractical |
| usability |
Critical usability problem
Improperly or inconsistently named or ordered item in main menu,
project contextual menu, editor contextual menu, new file wizard,
new project wizard and main toolbar. Proper and consistent naming
and ordering is defined in permanent UI specs.
|
| crash or deadlock | Intermittent crash or deadlock, happens fairly often |
| memory leak | Significant memory leak of a functionality which is used repeatedly |
| performance |
UI responsiveness of a feature breaking UI guidelines (100ms, 1s)
Significant scalability problem
AWT thread blocked by a task which could run on background
No or inappropriate indication of progress of a running task
|
| accessibility |
Opened window doesn't gain the focus directly but exists a workaround how to reach it
Missing Accessible Name (while Accessible Description is assigned)
|
| internationalization |
Any of the other non internationalization situations in this section
happen when user is running in other locale,
that does not happen when user runs in en locale,
that is also a P2 bug
For user using localized release, if a message or
label that come from the product does not come from a
localized file
User running in another locale than en uses characters
from that other locale but cannot see their representation
properly in the product
User types in or otherwise enters characters of the
locale they are running in, and the characters cannot be
entered at all or do not show properly in the product
Window or part of a window does not dynamially resize to
show all of it (up to maximum limit of screen size for entire window)
|
| others | Affects another developer's progress |
|
|
P3 |
| does not work | Part of a product feature is affected, a viable workaround exists |
| usability | Highly visible usability problem |
| memory leak | Small memory leak of a functionality which is not used often |
| performance |
Small performance problem
Bad use of API which causes waste of resources
|
| accessibility |
Illogical tab order
Inconsistent or non-standard methods of access by keyboard
Font, color is hardcoded
Mnemonic clashes inside of container
Missing Accessible Description (while Accessible Name is assigned)
|
| internationalization |
Product does not show the time and date
and any other locale specific information correctly.
(where such information does show correctly in the OS
and they are running in a locale supported for that by jdk and OS)
|
|
|
P4 |
| incorrect behavior | Incorrect behavior that doesn't affect functionality |
| usability | Minor usability problem |
| appearance | Incorrect visual appearance |
| performance |
Minor performance deficiency with minimal effect on a feature |
| accessibility |
Hardly understandable Accessible Name or Description (not expressed strictly but tells to user the correct meaning; HTML tags in text)
Missing mnemonic
No LABEL_FOR points to a component
|
|
|
P5 |
| minor annoyance | Causes unease, minor disturbance/annoyance |
| accessibility |
Typo in Accessible Name or Accessible Description
Mnemonic clashes in menu
|
