Issue Summary

Adding Approver for Status in Workflow of Request Type, when (a global) Approvers field (is added to the project's Fields, at Fields page; that global field is of type User Picker fyi), throws "Already exists. Try another name." error. User is told that they can Choose or Create a Field as shown below:

Documentation:

• https://support.atlassian.com/jira-service-management-cloud/docs/add-an-approval-to-a-request-type-in-team-managed-projects/
• https://support.atlassian.com/jira-service-management-cloud/docs/what-are-the-differences-in-classic-and-next-gen-approvals/

Issue is reproducible by Support

This is reproducible on Data Center: (unknown)

These custom approval fields generated during workflow approval step configuration can't be added to the Request Type layout.

Steps to Reproduce

1. in TMP Project settings -> Fields page, add "Approvers" global field (to the project)
2. Add Approvers field to Request Type layout (at Project settings -> Request type page)
3. Open Project settings -> Request type -> Edit workflow
   1. Select Status -> Approvals -> +
   2. In the Transitions for approval outcomes dialog box:
      1. Select Transition if approved from the pick list, Transition if declined (doesn't matter which ones) -> Next
   3. In the Approvers dialog box:
      1. Select Who chooses approvers? from choices (doesn't matter which option you choose)
      2. Enter the name of an existing User Picker field in the Approver field.  In this case enter 'Approvers'

Expected Results

Approvers field will be accepted and configurable with respect to the number of approvers that can and should be selected.

These custom approval fields generated during workflow approval step configuration can be added to the Request Type layout.

Actual Results

After entering the Approvers field, the following error is thrown:
Already exists. Try another name.

These custom approval fields generated during workflow approval step configuration can't be added to the Request Type layout.

Workaround

The workaround is to enter the name of an unused non-existing custom field name that can not be configurable to a defined list of approvers from which users can select which is not a reasonable workround. Note that if the field is used elsewhere, it will throw an error as well.

These custom approval fields (generated during workflow approval step configuration) can be seen (not edited) from filters as columnsadded to the Request Type layout.