Error when creating an issue from a security finding
Summary
Pressing the "Create an issue" button from a finding in a security dashboard (project or group level) will do nothing and report an error.
Steps to reproduce
- Go to https://staging.gitlab.com/groups/secure-team-test/-/security/dashboard/?scope=dismissed&page=1&days=90
- Find a vulnerability where an issue can be created
- Press the "Create an issue button"
- "There was an error creating the issue." is displayed and nothing happens
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
What is the current bug behavior?
(What actually happens)
- Error reported ("There was an error creating the issue.")
- Backend responds with
{"project_fingerprint":["can't be blank"]}
What is the expected correct behavior?
- Issue created for the corresponding finding.
Relevant logs and/or screenshots
See https://gitlab.com/gitlab-com/account-management/pre-sales/ssctechnologies/-/issues/6
/cc @matt_wilson for prioritization
Edited by Philippe Lafoucrière