M&O Prioritization
In order to triage incoming tickets, we're currently making use of the following priorities (defaulted to Medium)
JIRA Priorities #
| Name | Icon | Color | 
|---|---|---|
| Blocker | ||
| Major | ||
| Medium | ||
| Minor | ||
| Trivial | ||
| Backlog | ||
| Unknown | 
Blocker #
- Bug - Blocks development and/or testing work, production could not run. Crashes, loss of data, severe memory leak.
 - Enhancement - Vital to release. Time mandated deadline by legislature or grant
 - Task - Data fix that is preventing access or services for multiple end-users in production
 
Major #
- Bug - Major loss of function.
 - Enhancement - ex. code refactoring for maintainability, providing better UX on forms
 - Task - ex. Data fix that is preventing access or services for a single end-user in production
 
Medium #
- Bug - Impairment to functionality with time intensive or incomplete workaround.
 - Enhancement - Quality of Life enhancement which adds value to interface, process. Makes usage and maintainability easier or more efficient.
 - Task - Data quality or Data integrity fixes that are visible to users
 
Minor #
- Bug - Minor loss of function, or other problem where easy workaround is present.
 - Enhancement - Minor addition of business value from completing
 - Task - Data cleanup for internal use only data
 
Trivial #
- Bug - Cosmetic problem like misspelt words or misaligned text.
 - Enhancement - Minor UI tweaks. Addressing minor technical debt issues in code and documentation.
 
Backlog #
-   Bug - 
N/A - Enhancement - Work that can be completed as time allows. Ex. Efficiency improvements, non-critical lifecycle upgrades, technical debt
 - Task - Internal upkeep. Refactor data schema & normalization
 
Unknown #
- Bug -Unknown Priority at this time. For requester to review and assign.
 - Enhancement - Unknown Priority at this time. For requester to review and assign.