<!--- 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 When using grouped environment names deploy boards doesn't show up. By grouped i mean `backend/staging` + `backend/production` for example. Whe using classic environment names everything works as expected. ### Steps to reproduce Just create few grouped environments. ### What is the current *bug* behavior? When using grouped environment names deploy boards doesn't show up. ### What is the expected *correct* behavior? Expecting to work the same way as non-grouped environments. ### Relevant logs and/or screenshots   #### 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> System information System: Ubuntu 20.04 Proxy: no Current User: git Using RVM: no Ruby Version: 2.7.2p137 Gem Version: 3.1.4 Bundler Version:2.1.4 Rake Version: 13.0.3 Redis Version: 5.0.9 Git Version: 2.29.0 Sidekiq Version:5.2.9 Go Version: unknown GitLab information Version: 13.8.0-ee Revision: 1ae10d09692 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: 12.4 URL: https://gitlab.carvago.com HTTP Clone URL: https://gitlab.carvago.com/some-group/some-project.git SSH Clone URL: git@gitlab.carvago.com:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: no Using Omniauth: yes Omniauth Providers: bitbucket, bitbucket, bitbucket GitLab Shell Version: 13.15.0 Repository storage paths: - default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git </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> Checking GitLab subtasks ... Checking GitLab Shell ... GitLab Shell: ... GitLab Shell version >= 13.15.0 ? ... OK (13.15.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful Checking GitLab Shell ... Finished Checking Gitaly ... Gitaly: ... default ... OK Checking Gitaly ... Finished Checking Sidekiq ... Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 1 Checking Sidekiq ... Finished Checking Incoming Email ... Incoming Email: ... Reply by email is disabled in config/gitlab.yml Checking Incoming Email ... Finished Checking LDAP ... LDAP: ... LDAP is disabled in config/gitlab.yml Checking LDAP ... Finished Checking GitLab App ... Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 128/1 ... yes 7/2 ... yes 7/3 ... yes 7/4 ... yes 136/5 ... yes 7/6 ... yes 7/7 ... yes 7/8 ... yes 136/10 ... yes 7/11 ... yes 6/13 ... yes 6/14 ... yes 6/15 ... yes 6/16 ... yes 6/17 ... yes 6/18 ... yes 128/19 ... yes 5/20 ... yes 5/21 ... yes 5/22 ... yes 5/23 ... yes 5/24 ... yes 5/25 ... yes 129/26 ... yes 5/27 ... yes 129/28 ... yes 5/29 ... yes 5/30 ... yes 10/31 ... yes 10/32 ... yes 10/33 ... yes 7/34 ... yes 21/35 ... yes 60/37 ... yes 60/38 ... yes 129/39 ... yes 136/40 ... yes 5/41 ... yes 43/42 ... yes 60/43 ... yes 6/44 ... yes 6/45 ... yes 7/46 ... yes 5/47 ... yes 76/49 ... yes 76/50 ... yes 76/51 ... yes 6/52 ... yes 52/53 ... yes 5/54 ... yes 41/55 ... yes 52/56 ... yes 10/57 ... yes 6/58 ... yes 6/59 ... yes 5/60 ... yes 43/61 ... yes 60/62 ... yes 93/63 ... yes 86/64 ... yes 127/65 ... yes 5/66 ... yes 6/67 ... yes 32/68 ... yes 10/69 ... yes 5/70 ... yes 10/71 ... yes 133/72 ... yes Redis version >= 4.0.0? ... yes Ruby version >= 2.7.2 ? ... yes (2.7.2) Git version >= 2.29.0 ? ... yes (2.29.0) Git user has default SSH configuration? ... yes Active users: ... 120 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes Elasticsearch version 7.x (6.4 - 6.x deprecated to be removed in 13.8)? ... skipped (elasticsearch is disabled) Checking GitLab App ... Finished Checking GitLab subtasks ... Finished </pre> </details> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->