If a custom field with the same field name exists in a Next-Gen project, new issue types cannot be added

Issue Summary

If a custom field with the same field name exists in a Next-Gen project, new issue types cannot be added. The following message is displayed in the logs:

Error Messages: [Field with the same name already exists for this project.]

Steps to Reproduce

1. Create a Next-Gen project;
2. Create a custom field with the same name as a system field, for example, Resolution and save the changes.
3. Try to add the Issue Type.

Check this short video reproducing the behavior: Screen Recording 2019-11-06 at 06.10 PM.mov

Expected Results

Jira should not allow custom fields to be created with the same name as system fields.

Actual Results

An error message is displayed when trying to add the issue type.

Workaround

Rename any custom fields that could be related to system fields. If you are not sure which ones, please raise a ticket with Atlassian Support