Pipeline security dashboard view doesn't sort vulnerabilities according to severity and confidence

Summary

During testing in staging we realised that pipeline security dashboard view doesn't sort vulnerabilities according to severity and confidence.

Steps to reproduce

https://staging.gitlab.com/secure-team-test/webgoat/pipelines/12664449

Check dashboard

Example Project

https://staging.gitlab.com/secure-team-test/webgoat/

What is the current bug behavior?

image

What is the expected correct behavior?

Medium confidence elements should be listed first

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of: sudo gitlab-rake gitlab:env:info)

(For installations from source run and paste the output of: sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of: sudo gitlab-rake gitlab:check SANITIZE=true)

(For installations from source run and paste the output of: sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)

(we will only investigate if the tests are passing)

Possible fixes

Sort fields according to their enum values rather than string values

Edited Oct 21, 2019 by Can Eldem
Assignee Loading
Time tracking Loading