Issue Summary

If you create a custom field in a team-managed (formerly next-gen) Project and the name already exists in the company-managed (formerly classic) global custom fields, using the field in a JQL search will break, causing any existing filters using this field to fail.

Steps to Reproduce

1. Load the existing filter which has the custom field as part of JQL Or create a custom field in the Company Managed Project and save it as a filter.
2. Create a custom field in the Team Managed Project with exact name of the field in the Company Managed Project.
3. Open or reload the saved filter created in step 1.

Expected Results

The JQL basic and advanced search should recognise these are 2 different fields and continue to function accordingly.

Actual Results

All the existing filters will break that has this custom field with below error:

 

Workaround

• Delete the custom field that's created in the Team Managed Project Or,
• Simply rename one of the custom fields so there are no duplicates.