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.
- Security holes with a clear exploit possible
- Regressions that break currently working systems
- 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)
- Average run of the mill bug
- 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.
- Backend
- Metabase Developer Reference
- Product Management
- QA and Testing
- Writing A Driver
- Driver Notices
- REST API Notices
- Writing style guide for documentation and blog posts (WIP)