-
Bug
-
Resolution: Not a bug
-
High
-
17
-
Severity 3 - Minor
-
6
-
Issue Summary
Customers report that searching for custom fields that share the same name using advanced searching does not show all of the fields unless they're different field types.
Steps to Reproduce
- Have two or more custom fields named the same and share the same field type.
- Perform a JQL search with the field name. The autocomplete suggestions only show a single field and not all of the possible fields as before.
Expected Results
Previously the autocomplete suggestions showed the fields with their field IDs for duplicates and all of them could be added in the JQL search. This is the expected behavior.
Actual Results
The completion suggestion shows only one of the duplicated fields with no ID. This leads to JQL searches dismissing duplicate fields unless the CF ID is used.
Workaround
- Perform JQL searches using the custom field ID.
- To obtain the custom field IDs please visit your instance's Custom Field configuration page by navigating to Jira settings > Issues > Custom Fields and find the fields in the list. Then click on the three dots at the end of the row for each field and click Edit details. In the resulting page you'll find the Custom Field ID at the end of the browser's URL.
- Change the names of the custom fields. This will not impact the existing data in the issues that use the field.
- is related to
-
JRACLOUD-74239 Creating a custom field with same name and context as another custom field leads to error in Advanced search
- Closed
- relates to
-
JRACLOUD-75453 JQL breaks with company-managed (formerly classic) custom fields if a team-managed (formerly next-gen) duplicate exists
- Closed
-
JRACLOUD-76536 JQL "custom field" is EMPTY does not work when there are other custom fields with the same name
- Closed