No issues found with certain words, although existing
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
When searching in gitlab.com issues certain words have a strange behaviour. Seems to be a Feature not a bug. I didn't find any documentation about it. there is no hint in the UI when this happens. When only those words, the result is just empty, when other words those strings are just ignored.
Strings that are ignored are:
after, or, is, and, not, has, for, will, can't, more, are and more
Example of other strings, that are not ignored are:
due, isn't, less, soon, lot, w
What is the advantage of doing so?
Is this a relict from times when gitlab.com had performance problems when searching for issues?
As well, I want to be able of adding words like "more" or "don't" to fine tune my searches if the already existing words return too many results. Adding those words to existing strings doesn't alter the search result at all. Why?
Steps to reproduce
There seems no bug report here with the word after:
https://gitlab.com/gitlab-org/gitlab/-/issues/?label_name%5B%5D=type%3A%3Abug&search=after
And no issue at all for the whole repo with that word:
https://gitlab.com/gitlab-org/gitlab/-/issues/?search=after
Example Project
What is the current bug behavior?
I was searching for that issue and it doesn't give me any result when searching the word 'after'
What is the expected correct behavior?
- Don't ignore those words?
- or explain me the used word is excluded from the searches when using them, instead of saying: "no issues with that word"?
- Mark the ignored words red? or cross them out. or delete them out of the form.
Relevant logs and/or screenshots
Output of checks
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)