Skip to content

WIP: Issue taxonomy changes: single priority field, new severity field, team boards

Eric Johnson requested to merge issue-taxonomy into master

Why was this MR needed?

  1. 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?
  2. 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
  3. 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?

  1. This collapses priority into a single label set and forces the different stakeholders to reconcile their concerns
  2. This creates separate severity label set
  3. Replaces the team label with the requirement to place an issue on the appropriate team's backlog

To do's

  1. Socialize with Quality, Security, and Support to draft proposal
  2. Get input buy-in from Product and development to finalize proposal
  3. Get sign-off from DZ, Sid
  4. Edit the project label page
  5. Create the team boards
  6. Use queries to re-groom issue backlog
  7. Edit/remove other pages that talk about old taxonomy (e.g. security handbook page)

Does this MR meet the acceptance criteria?

Edited by Eric Johnson

Merge request reports