Adding a group with a long name to Merge requests approval rules does not work
Summary
When adding a group to merge request approval rules, it seems not to work when the group name is long.
Steps to reproduce
Create a group with a long name (100 characters or more) Add some members to the group Try to add the group to a Project's merge request approval rules
Example Project
What is the current bug behavior?
When you add a group with a long name to a project's merge request approval rules, the action is not successful. There are no errors displayed on the screen. Adding a group with a shorter name is successful.
What is the expected correct behavior?
Users should be able to add groups to their projects' merge approval rules, regardless of the length of the group name.
Relevant logs and/or screenshots
- Moved the reproduction video to the associated customer collaboration project issue to protect privacy of the customer info. If you have problem of accessing the video, please let me know @bma.
Output of checks
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)