#1581 Issue: Sorting the Compliance Alerts of each project based on thier Severity level #1612
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
…ct based on the requirements error->warning->missing->empty string Signed-off-by: shuchitachawla2909 <[email protected]>
shuchitachawla2909
force-pushed
the
compliance_alerts_sort
branch
from
3234cf0 to
bda240e
Compare
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.
Hello @pombredanne
Addressing Issue #1581
We want the order of severity levels as: error > warning > missing > '' (empty string) on a high level priority policy.
Earlier the dictionary storing the Severity levels of each project was not sorted, made changes to enforce the priority level.
Now the Compliance Alerts Panel will show all projects in uniform order.