"Select project to create issue dropdown" returns 500 when no input provided
Summary
On my Issues dashboard, when clicking the "Select project to create issue dropdown" dropdown, GitLab returns a 500 when no inputs are entered. It is not able to give the list of Projects unless characters are typed in. Once characters are typed in, it works just fine.
Steps to reproduce
Since I only have my 1 GitLab account, I can only give the steps to reproduce that worked for me, consistently. I am not sure if this bug is related to the specific data associated with my GitLab account (it may be)
- Log in to my account snackattas
- Click the Issues button in the right corner of the navbar which takes me to https://gitlab.com/dashboard/issues?assignee_username=snackattas
- Open the "Select project to create issue dropdown" dropdown in the upper right corner. Don't type anything, and the endpoint https://gitlab.com/api/v4/projects.json?search will return a 500, preventing you from getting a list of Projects
As soon as you type, you are able to get a list of Projects that matches your search criteria. You just can't get a list of all Projects without typing.
Example Project
Does not seem to be related to individual Projects.
What is the current bug behavior?
As stated, the dropdown, without input, does not return a list of all Projects.
It seems the with_issues_enabled=true
parameter is the one causing issues
When testing each parameter in Postman, it is its easy to see that with_issues_enabled is the problem parameter
When with_issues_enabled=false, the endpoint returns data
When with_issues_enabled=true and search terms are provided, it works
When with_issues_enabled=true and search terms are provided that don't match anything, it still works
What is the expected correct behavior?
The correct behavior is that, when clicking
Relevant logs and/or screenshots
Output of checks
This bug happens on GitLab.com
Results of GitLab environment info
My GitLab account is very new and I only have 3 projects if that makes a difference. I have created a test issue on one of my projects, and the endpoint still 500s.
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
This happened on my personal GitLab account...I would try other things to repro this, but as I only have access to my one account, I couldn't do more troubleshooting
(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)