When filtering by "Not connected", the selection results in an error
Summary
When filtering by "Not connected" in the Runners admin section, the selection results in an error
Steps to reproduce
- Visit the admin section of GitLab Runners http://gdk.test:3000/admin/runners
- Select "Status" in the filter bar
- Select "Not connected"
What is the current bug behavior?
The filtering fails as we send the filter "Not connected"
to the API instead of NOT_CONNECTED
What is the expected correct behavior?
Runners are filtered, so "Not connected" runners appear.
Relevant logs and/or screenshots
Please note the URL bar below:
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`)
Possible fixes
This issue seems to originate in the gitlab-ui components input/value, given two example options:
options: [
{ value: STATUS_ACTIVE, title: s__('Runners|Active') },
{ value: STATUS_NOT_CONNECTED, title: `"${s__('Runners|Not connected')}"` },
],
The options without space correctly use the value
, while use value
as the title
.
An option without spaces | An options with spaces |
---|---|
Edited by Miguel Rincon