<!--- 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 updating health status via sidebar on issues, an error banner appears and the update fails.  ### Steps to reproduce 1. Go to an issue 2. On the sidebar, select a health status 3. Observe red banner 4. Reload. No update. ### 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. --> This is the issue I tested it on: https://gitlab.com/issue-reproduce/charliecharlie123/-/issues/10 ### What is the current *bug* behavior? The health status does not update, and a red banner appears. ### What is the expected *correct* behavior? The health status should update with no error. ### Relevant logs and/or screenshots Browser info for updating https://gitlab.com/issue-reproduce/charliecharlie123/-/issues/10 <details> <summary>Request payload</summary> ``` [{"operationName":null,"variables":{"healthStatus":"onTrack","projectPath":"issue-reproduce/charliecharlie123","iid":"10"},"query":"mutation ($projectPath: ID!, $iid: String!, $healthStatus: HealthStatus) {\n updateIssue(input: {projectPath: $projectPath, iid: $iid, healthStatus: $healthStatus}) {\n issue {\n healthStatus\n __typename\n }\n errors\n __typename\n }\n}\n"}] ``` </details> JSON output: <details> <summary>JSON response body</summary> ``` [{"errors":[{"message":"InputObject 'UpdateIssueInput' doesn't accept argument 'healthStatus'","locations":[{"line":2,"column":61}],"path":["mutation","updateIssue","input","healthStatus"],"extensions":{"code":"argumentNotAccepted","name":"UpdateIssueInput","typeName":"InputObject","argumentName":"healthStatus"}},{"message":"Variable $healthStatus is declared by anonymous mutation but not used","locations":[{"line":1,"column":1}],"path":["mutation"],"extensions":{"code":"variableNotUsed","variableName":"healthStatus"}}]}] ``` </details> ### Output of checks <!-- If you are reporting a bug on GitLab.com, write: 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> #### Workaround * Go to issue list (in the breadcrumbs, click "Issues")  * Click "Edit Issues" button on the top right  * Select your issue  * Select the health status  * Click "Update All" at the top  ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->