WIP: Issue taxonomy changes: single priority field, new severity field, team boards
Why was this MR needed?
- Currently priority is captured in separate labels for support, security, and product. While this allows for granularity, it also allows us to avoid making the hardest decision: At the end of the day, what should we be working on?
- We are also missing a way to capture the severity of bugs or security incidents separate from priority. This is important because priority may be a combination of severity and effort. But we don't want to lose the account of severity
- We are not using boards in our own product effectively. And doing so is a way to reduce label noise, specifically to replace the team labels. Placing issue on boards is also more actionable than a label
What does this MR do?
- This collapses priority into a single label set and forces the different stakeholders to reconcile their concerns
- This creates separate severity label set
- Replaces the team label with the requirement to place an issue on the appropriate team's backlog
To do's
- Socialize with Quality, Security, and Support to draft proposal
- Get input buy-in from Product and development to finalize proposal
- Get sign-off from DZ, Sid
- Edit the project label page
- Create the team boards
- Use queries to re-groom issue backlog
- Edit/remove other pages that talk about old taxonomy (e.g. security handbook page)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together -
Internationalization required/considered
Edited by Eric Johnson