Critical case severity #939
Merged
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
Closed
|
@zpriddy Are you still considering adding this? I think it would be a valuable feature. |
|
Yes I am, just waiting for it to get merged |
|
I added this in our own instance two years or so back as well because of internal "needs", but the point still stands: every company has their own definition of severity levels where it has to align with other departments and services, which is why I didn't make a pull request for it. Some have information -> critical (5), while others have low -> high (3), etc. Great work on your end, but I personally think it's wrong to just add another level rather than have the "custom" way be possible. |
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.
Add critical severity ( Replaces #926)