/rest/api/3/workflowscheme/update doesn't update inactive workflow schemes

Issue Summary

It's not possible to update inactive workflow schemes using the new Update workflow scheme /rest/api/3/workflowscheme/update API endpoint.

Steps to Reproduce

• Create a workflow scheme, using UI or REST API; but don't associate it with a project.

   curl --location 'https://your-domain.atlassian.net/rest/api/3/workflowscheme' \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Basic <api_token>' \
  --data '{
    "defaultWorkflow": "jira",
    "description": "The description of the example workflow scheme.",
    "name": "Example workflow scheme"
  }'
  

• Get it's version information using /rest/api/3/workflowscheme/read Bulk get workflow schemes

  curl --location 'https://your-domain.atlassian.net/rest/api/3/workflowscheme/read' \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Basic <api_token>' \
  --data '{
    "projectIds": null,
    "workflowSchemeIds": [
        <id_of_the_created_workflow_scheme>
    ]
  }'
  

• Try to update the workflow scheme, using /rest/api/3/workflowscheme/update

  curl --location 'https://your-domain.atlassian.net/rest/api/3/workflowscheme/update' \
  --header 'Accept: application/json' \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Basic <api_token>' \
  --data '{
      "description": "Tyring to update the description of the workflow scheme",
      "id": "<id_of_the_created_workflow_scheme>",
      "name": "Example workflow scheme",
      "defaultWorkflowId": "jira",
      "version": {
              "versionNumber": <int>,
              "id": "<guid>"
      }
  }'
  

Expected Results

workflow scheme should be updated. same as active workflow schemes (that are associated with a project)

Actual Results

We receive a 200 OK (with no response body) but the scheme isn't actually update.

Workaround

Currently there is no known workaround for this behaviour. A workaround will be added here when available