Open issuesSwitch filter

Currently in Jira there can be multiple 'Linked issues' fields in a single site.

• Customers using Jira Product Discovery will have an additional custom field added to Jira named 'Linked issues'.
• Third party Marketplace Apps may add 'custom formulas', which are also named 'Linked issues'.
• When there are multiple fields named 'Linked issues' in Jira, the JQL searches auto-populate all of the 'linked issues' fields when trying to search, making it very confusing to know which field is the correct field. 

We are encountering critical system integrity issues due to the handling of custom fields in Jira and Jira Product Discovery (JPD), and I am 99% certain this has already been flagged via an existing feature request.

The root of the problem stems from the following:

1. Jira allows the creation of fields with duplicate names.
2. Jira allows custom fields to be created with the same name as standard/system fields.
3. JPD introduces a large volume of fields with overlapping or identical names.

This behavior creates significant disruption:

• Uncontrolled field duplication across Jira's ecosystem undermines data consistency. When field names are repeated, it becomes nearly impossible to distinguish which is correct, particularly in filters, dashboards, and automation.
• We have been forced to pause our adoption of JPD due to the chaos caused by duplicated fields.
• We have disabled the use of Team-Managed projects in our instance to avoid further proliferation of custom fields.
• The resulting confusion leads to a loss of user trust in the platform. When users pick the wrong field unknowingly, they receive misleading results, which compromises the credibility of reports and search outputs.
• Administrative overhead becomes unmanageable. Admins must constantly explain, investigate, and mitigate duplicated field usage—adding no value but consuming significant time.
• These issues also lead to unnecessary support requests to Atlassian, many of which could be prevented with stricter field creation rules or naming controls.

We strongly urge Atlassian to:

• Prevent field creation with duplicate names.
• Warn or block users when attempting to create a field that matches an existing system or custom field.
• Review how JPD and Team-Managed projects handle field generation, especially in shared environments.

Until these issues are resolved, our ability to scale within the Atlassian ecosystem is significantly hindered.