Issue Tracker Priority definition


P1
Blocker
Extremely urgent, fix or patch immediately
  • Data Corruption
  • Major feature not working without workaround
  • Show stopper - 2 or more systems/groups affected
  • Stops whole test module (including CTS) from running
  • Server doesn't start, or crashes without workaround

P2
Critical

Fix or patch required for the next external release
  • CTS failures or spec issues
  • Legal issues
  • Error messages in some areas identified by QA (either Critical/P2 or Major/P3)
  • Urgent - 1 system/group is affected
  • Blocks significant number of tests or people from making progress
P3
Major
Fix required for FCS
  • Bugs with workaround to get fixed
  • RTM requirement
  • Packaging issues
  • Major usability issues
  • I18N / L10N bugs
  • Missing error message in general
  • Spelling errors for INFO/WARNING/SEVERE message text
P4
Minor
Fix desired for FCS
  • Internal or invisible to customer
  • Minor usability issues or those with easy workarounds
P5
Trivial
Fix not required for FCS
  • Most RFEs
  • Cosmetic UI issues that don't impact usability
  • Spelling errors in general

Acronyms: