<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Bug related to scoping on issues Board on gitlabl.com I'm trying to scope an (issue) board with a sub-group label : I can see and select the right label in "Edit board" section, but when I click on "save changes" it is not taken into account. Note: When I try to filter result in the search/filter bar of the board, I can effectively filter by my sub-group label. However, it's not a scoped board anymore and need to be filtered each time. ### Steps to reproduce - Create the following structure : - groupA - subgroupA - myproject - add a group label "mysubgrouplabel" in subgroupA - add two issues in myproject, only one with the "mysubgrouplabel" - create a board in groupA - click on "edit board" and try to scope by the label "mysubgrouplabel" ### 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. --> Example structure and project : https://gitlab.com/scopopop/gitlab-bugs/groupa The board "board_to_scope" : https://gitlab.com/groups/scopopop/gitlab-bugs/groupa/-/boards/2777747 ### What is the current *bug* behavior? <!-- Describe what actually happens. --> Selecting the label works correctly. When saving changes, it reload the page but nothing changed. When going back to "edit board" section, the previous selected label disappeared. ### What is the expected *correct* behavior? <!-- Describe what you should see instead. --> It should scope issues in the board by the selected label. ### 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. --> ### Output of checks This bug happens on GitLab.com #### Results of GitLab environment info <!-- Input any relevant GitLab environment information if needed. --> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (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`) </pre> </details> #### Results of GitLab application Check <!-- Input any relevant GitLab application check information if needed. --> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (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) </pre> </details> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->