When I initially tried to 'Create issue' using the button at the bottom right, it simply said 'Error', with no explanation (issue 2 only)
Scope of Issue
Below you can read the steps to reproduce, as part of this issue we are ONLY addressing the experience of when initially trying to 'Create issue' using the button at the bottom right, it simply returns 'Error', with no explanation. After time passes, clicking 'Create issue' worked fine.
Summary
I cloned an OWASP Web Application project (OWASP Benchmark) into gitlab at: https://gitlab.com/wichers/benchmark
And the first thing I did was to enable the AppSec tools scanner w/AutoDevOps enabled. Most of the scans ran fine, and when I looked at the Container Security issues identified I ran into three issues.
Steps to reproduce
- Run the AppSec tools on a project that includes 1 or more Docker containers
-
Immediately after it is complete, look at a Container Security issue:
Issue: 1) The container being scanned was not listed in the issue.- Issue: 2) 'Create issue' function simply returns 'Error'.
- For a public repository, where security issues are found, it doesn't appear you can fork it into a private repo so you can create a private pull request to fix the issue.
Example Project
https://gitlab.com/wichers/benchmark
What is the current bug behavior?
Issue: 2) When I initially tried to 'Create issue' using the button at the bottom right, it simply said 'Error', with no explanation. Later on, (I tried 3 days later), it worked fine.
This was confusing/unexpected.
What is the expected correct behavior?
Issue 2) If 'Create issue' won't work for a new issue for a little while until things 'catch up', Gray out the button and explain what it is waiting on, or provide a useful error message explaining why it can't create the issue now, and when the can expect to be able to.
Relevant logs and/or screenshots
None
Output of checks
This bug happens on GitLab.com.
Possible fixes
See correct behavior explanation.
Linked Issues
- For a public repository, where security issues are found, it doesn't appear you can fork it into a private repo so you can create a private pull request to fix the issue.
- "The container being scanned was not listed in the issue"
- When I initially tried to 'Create issue' using the button at the bottom right, it simply said 'Error', with no explanation