<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label. For the Community Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug For the Enterprise Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary (Summarize the bug encountered concisely) The environment selector on the metrics dashboard page doesn't actually change the environment. Selecting a different environment doesn't do anything. ### Steps to reproduce (How one can reproduce the issue - this is very important) 1. Create 2 or more environments under *Operations > Environments*. Name one of the environments `production` for convenience. 1. Do a deployment to atleast one of the environments, preferably the production environment (to avoid [this bug](https://gitlab.com/gitlab-org/gitlab-ee/issues/11164)). 1. Go to *Operations > Metrics*. If you deployed to production environment in the previous step, the production metrics should open up. If not, it will open the production environment metrics anyway and show a "No data found" empty state which doesn't have the environment selector (as of June 13th 2019), so you pretty much have to deploy to production in order to see the environment selector. 1. Try selecting a different environment from the environment selector. 1. Nothing happens when you select anything in the environment selector dropdown.  ### 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) https://gitlab.com/rpereira2/autodevops-deploy2/environments/749475/metrics (Comment on this issue and I will grant access) ### What is the current *bug* behavior? (What actually happens) Selecting an environment in the environments selector on the metrics dashboard does nothing. ### What is the expected *correct* behavior? (What you should see instead) Selecting an environment in the environments selector should take the user to the metrics dashboard for that environment. ### 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 (If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com) This bug happens on GitLab.com #### Results of GitLab environment info <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 <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)