Group Security Dashboard: Sort all vulnerability history keys
What does this MR do?
It was discovered that the graphing of cached vulnerability history is incorrect sometimes because the dates of the vulnerabilities for the severities is assumed to be sorted. This change ensures that the dates are sorted appropriately.
https://gitlab.com/gitlab-org/gitlab-ee/issues/11693#note_203338736
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation created/updated or follow-up review issue created -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Performance 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
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
Edited by rossfuhrman