Create a new label

Create a new label Critical-P1 for tickets that require same-day engineering attention and add a distinct red color. Notify Alex and the on-call engineer when the label is used, and ensure it's only available to support leads to apply.

Before we add Critical-P1, structure it so reviewers act: put the expected SLA in the label name, make a short description saying who must be notified, and list two examples of issues that warrant the label so others don't overuse it.

I want a Critical-P1 label for same-day engineering issues but worry everyone will slap it on. The on-call engineer and I disagree on scope. What's the likely point of contention, and what narrowly worded label name and two-sentence application rule will make misuse unlikely while keeping the team responsive?

Our mailbox has exploded with labels over time, making it hard to find the right one during incidents. This recurring pattern wastes minutes that add up to hours across the team. What habit should I change to stop label bloat — propose a naming convention, a retirement rule, and the one-line checklist to use before creating a new label.