Refine issue prioritization criteria in Governance.md #4667
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
Alan-Jowett
approved these changes
Sep 25, 2025
dthaler
reviewed
Sep 26, 2025
| 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). |
Collaborator
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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