Add priority calculation logic to reach calculator #259
Conversation
This file contains 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
kzar
force-pushed
the
sbt-priority
branch
4 times, most recently
from
7fe0ec8 to
53b9fa5
Compare
Folks using the site breakage reach calculator have to then check the severity matrix spreadsheet manually when assigning a "Priority" label to site breakage tasks. Why not include that logic here, to save folks time? We can also include some of the severity examples here from Asana, to save folks needing to look those up separately.
tagawa
approved these changes
Feb 20, 2025
kdzwinel
approved these changes
Feb 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Folks using the site breakage reach calculator have to then check the severity
matrix spreadsheet manually when assigning a "Priority" label to site breakage
tasks. Why not include that logic here, to save folks time?
We can also include some of the severity examples here from Asana, to save folks
needing to look those up separately.