GitLab project does not appear in the list when adding an issue to a new board.

Summary

(Summarize the bug encountered concisely)

Typing GitLab.org / gitlab is unable to find a matching project to add an issue to when creating a new issue from a board. Interestingly, typing end-to-end for the project name is able to find it.

This means I am unable to add a new issue from the board directly. As a workaround, I click into an issue in the project, then use the New issue button in the banner to add the issue.

Some discussion in Slack was at https://gitlab.slack.com/archives/C0AR2KW4B/p1570542771230100 about this.

Steps to reproduce

(How one can reproduce the issue - this is very important)

  1. Go to a planning board
  2. Under a given milestone, click the plus button
  3. Under Project, type GitLab.org / GitLab
  4. See No matching results

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)

https://gitlab.com/groups/gitlab-org/-/boards/1183657?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=Secure%3A%3AStatic%20and%20Dynamic%20Analysis&label_name[]=direction&weight=None

What is the current bug behavior?

(What actually happens)

Typing GitLab.org / gitlab in the project screen is unable to locate a project to add an issue to.

What is the expected correct behavior?

(What you should see instead)

Typing GitLab.org / gitlab in the project screen is able to successfully find the project to add the new issue to.

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.)

image

image

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

(If you can, link to the line of code that might be responsible for the problem)

Edited by Sam Kerr