Labels List

Labels are intended to be used in groups. Some of these (high-priority, medium-priority, mild-annoyance) are specifically about the priority of the issue for users. Others (need-more-info and quick-fix) have more to do with how the bug will be perceived by developers, though they may be relevant to users as well. A bug might be both a medium-priority and a quick-fix, or a mild-annoyance and need-more-info.

• affects-dispatch: Visible to / problematic for dispatch users. (Might or might not also be visible to volunteer users.)
• affects-volunteers: Visible to / problematic for volunteer users. (Might or might not also be visible to dispatch users.)
• done-needs-merge: Fixed on a branch, but needs to be merged into master.
• deferred: On hold. Not to be fixed at the moment.
• high-priority: Deemed to be exceptionally important; needs to be fixed as soon as possible. These are usually bugs that are having a noticeable impact on users and preventing proper use of the system.
• medium-priority: Should be fixed soon, but isn't as much of a "showstopper" as the high-priority label implies. Users likely have a workaround, but the bug is still slowing them down.
• merged-needs-deploy: Done and merged to master (or deployment branch), but has not been deployed to production server(s).
• mild-annoyance: Doesn't really impact work flow, but is still a problem for users. Lowest priority.
• need-more-info: Unclear explanation and/or lacking a reproduction case. More information requested from the reporter or someone else with knowledge of the issue.
• quick-fix: Indicates an easy bug to handle, independent of severity on the user side.

More labels will be added as needed. We will continue to document them here.