<!--- 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 E2E test for [contribution_analytics_spec.rb](https://gitlab.com/gitlab-org/gitlab/-/blob/master/qa/qa/specs/features/ee/browser_ui/3_create/contribution_analytics_spec.rb) is failing because it wasn't able to close the issue. Clicking the "Close Issue" button doesn't fire any event. I was able to reproduce this in my local GDK, screenshot provided below ### Steps to reproduce (Steps from the above test) - Login - Visit an issue (in the issue list, click on the issue) - On the issue page, click on "Close Issue" button (the one on top, the bottom one is working fine) ### What is the current *bug* behavior? No event is fired, issue is not closed. ### What is the expected *correct* behavior? Event is fired, issue is closed ### Relevant logs and/or screenshots  ### Output of checks This test is failing in Staging and master pipelines see https://gitlab.com/gitlab-org/gitlab/-/issues/219175 for failure tracking records #### 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) ### Workaround Use the bottom `Close Issue` button or use the `/close` quick action. ### Support Tickets (internal) 1. https://gitlab.zendesk.com/agent/tickets/158676 1. https://gitlab.zendesk.com/agent/tickets/158651