This repository has been archived by the owner on Dec 14, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 30
Bug Triage
Dennis Jen edited this page Jul 1, 2020
·
4 revisions
We triage issues tagged with the bug label regularly. See the bug triage board for current priorities.
Definition via wikipedia:
A software bug is an error, flaw or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.
Enhancements and new features will follow the standard development process (TBD).
Bugs are triaged according to the following criteria:
| Priority | Criteria | Next Steps & Timeframe |
|---|---|---|
| Low | - Friction on non-core UI paths (e.g. misaligned buttons) - Displaying non-critical addition information/metadata (e.g. story level drill downs) |
These are worth tracking, but unlikely to be addressed |
| Medium | - A workaround exists, but it’s cumbersome | These are considered non-interrupting issues and will be pulled into the development cycle. Timeframe: weeks |
| High | - Reporting incorrect data (e.g. duplicate data) - UI friction on a core path - Something that bothers a lot of people (e.g. confused on how to download a CSV, it’s possible, but difficult) - Blocking progress on a research project |
Addressing these issues interrupted current work. We will actively work to fix these. Timeframe: days |
| Won't Fix | - Broken or not needed by an ongoing research project | Mark as won’t fix and close |
| Remove | - Incomplete feature - Unused functionality |
Remove the code |
We love improving our process. It can and should change and be adapted to our evolving needs.