Skip to content

Bug Prioritization

Sameer Al-Sakran edited this page Apr 10, 2019 · 3 revisions

Want to know how we prioritize issues (or perhaps help triage?!) ?

Here's a quick overview.

P0 - Critical Bug

Fix immediately and put out a patch release

  • Security holes with a clear exploit possible
  • Regressions that break currently working systems

P1 - Urgent

Fix in the next release

  • Security holes without a clear exploit (eg, potential escalations, etc)
  • Crashing the server or the browser
  • Anything related to
    • Setup/Upgrade
    • Login
    • Outright breaking of commonly used features (querybuilder, dashboards, line charts, etc)
    • Correctness (eg Timezones)

P2 - Major

Fix when we can

  • Average run of the mill bug

P3 - Minor

Fix if it is easy

  • Cosmetic bugs
  • Minor bugs that have a clear workaround

In general, if something affects lots of users, bump it up one level. If it's only reported by one person and you think it is limited in scope bump it down one level.

Clone this wiki locally