Resolve "Fix severity and status sort order on alert list"
What does this MR do?
Fixes #221242 (closed)
Changes AlertManagement::Alert severity sort order:
- Ascending sort order sorts severity from less critical to critical.
- Descending sort order sorts severity from critical to less critical.
Changes AlertManagement::Alert status sort order:
- Ascending sort order sorts statuses: Ignored > Resolved > Acknowledged > Triggered
- Descending sort order sorts statuses: Triggered > Acknowledged > Resolved > Ignored
Screenshots
Sort by severity
Sort by status
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
~~Label as security and @ mention @gitlab-com/gl-security/appsec~~ -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team