Refine issue prioritization criteria in Governance.md #4667
Conversation
Clarify criteria for P1, P2, and P3 issue labels regarding business impact and milestone settings.
mingxr
requested review from
Alan-Jowett,
LakshK98,
dthaler,
matthewige,
mikeagun,
mtfriesen,
poornagmsft,
saxena-anurag and
shankarseal
as code owners
| This label represents highest priority. This label should ONLY be applied to bugs or features with quantifiable business impact. Quantifiable business impact may include number of users, business blocked, or deployment blocked. Bugs with only qualitative impact (descriptions without numbers) will be ranked lower than quantifiable P1 bugs. `P1` issues MUST be set to the *current milestone*. | ||
| ### P2: | ||
| This label is used for the next level of priority. Issues marked as `P2` can be set to the current milestone or to a future milestones (preferred). | ||
| This label is used for the next level of priority. Issues marked as `P2` will be set future milestones (preferred). |
There was a problem hiding this comment.
This change doesn't make sense to me. If there's already an open pull request (e.g. from a community member) and it's early in the month, what's the point of saying it "will" be set to a future milestone? I think this line should be kept as is.
There was a problem hiding this comment.
Pull request overview
This PR refines the issue prioritization criteria in the Governance documentation to better align with the growing team and partner ecosystem. The key change elevates the bar for P1 issues by requiring quantifiable business impact metrics.
- P1 label now requires quantifiable business impact (e.g., number of users affected, business blocked, deployment blocked) rather than just urgency
- P2 and P3 milestone settings have been clarified to better distinguish priority levels
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| This label represents highest priority. This label should ONLY be applied to bugs or features with quantifiable business impact. Quantifiable business impact may include number of users, business blocked, or deployment blocked. Bugs with only qualitative impact (descriptions without numbers) will be ranked lower than quantifiable P1 bugs. `P1` issues MUST be set to the *current milestone*. | ||
| ### P2: | ||
| This label is used for the next level of priority. Issues marked as `P2` can be set to the current milestone or to a future milestones (preferred). | ||
| This label is used for the next level of priority. Issues marked as `P2` will be set future milestones (preferred). |
There was a problem hiding this comment.
Grammar error: "future milestones" should be preceded by an article. The sentence should read "Issues marked as P2 will be set to future milestones (preferred)." to be grammatically correct.
| This label is used for the next level of priority. Issues marked as `P2` will be set future milestones (preferred). | |
| This label is used for the next level of priority. Issues marked as `P2` will be set to future milestones (preferred). |
| This label is used for the next level of priority. Issues marked as `P2` will be set future milestones (preferred). | ||
| ### P3: | ||
| This label is used for low priority issues. Issues marked as `P3` can be set to any future milestone or the `Backlog` milestone. | ||
| This label is used for low priority issues. Issues marked as `P3` can be set to future milestones beyond 3 month or the `Backlog` milestone. |
There was a problem hiding this comment.
Grammar error: "month" should be plural "months" when following the number 3. The phrase should read "future milestones beyond 3 months" to be grammatically correct.
| This label is used for low priority issues. Issues marked as `P3` can be set to future milestones beyond 3 month or the `Backlog` milestone. | |
| This label is used for low priority issues. Issues marked as `P3` can be set to future milestones beyond 3 months or the `Backlog` milestone. |
3 participants
Clarify criteria for P1, P2, and P3 issue labels regarding business impact and milestone settings.
Description
Changing the definition of P1 bugs as our team and partners grow in size.
This will trigger a revisit of bugs currently tagged as P1. If quantifiable business impact is available, they need to be added for bugs to remain as P1. Ming can provide assistance for potential tough cuts.
Testing
No
Documentation
Changing the definition of P1 bugs.
Installation
No