Issue Summary

The fields menu in company-managed projects (plugins/servlet/project-config/{projectid}/fields) displays all fields in the Default Field Configuration including team-managed  fields. This can cause inconsistencies in the display of fields on the various screens and may cause confusion to the users.

When you add a similarly named field in company-managed projects, the Team managed project in  Default Field Configuration is replaced.  If you deleted the added field from Custom Fields, It reverts to displaying the team-managed  field in Default Field Configuration

This is happening for Jira Software projects.

Steps to Reproduce

1. Create a custom field in a team-managed  project.
2.  Navigate to a company-managed project which uses the default field configuration
3. Navigate to project settings → fields
4. Inspect the list of fields in the default field configuration. The team-managed  field will be listed over here.
5. Create Custom field of same type and and as the Team managed project field.
6.  Navigate to a company-managed project which uses the default field configuration configuration and observe the change.
7. Delete the Custom field from Custom fields.
8. Navigate to a company-managed project which uses the default field configuration configuration and observe the change. 

Expected Results

The team-managed  fields should not show up under the Fields configuration of company-managed  projects.

Actual Results

The team-managed  fields show up under the Fields configuration of company-managed  projects which is using Default Field Configuration.

Workaround

NA

Similar closed bug  https://jira.atlassian.com/browse/JRACLOUD-75684