-
Bug
-
Resolution: Won't Fix
-
High
-
1
-
Severity 3 - Minor
-
3
-
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 is causing problems:
- Relocating the field in the filter makes the custom field disappear.
- CSV Export of the filter with the custom field added, shows duplicate fields.
Steps to Reproduce
- Create a Custom Field in Team Managed Project, with the same name as a field in Global Settings -> Custom Fields.
- Use JQL in Company Managed Project, add the Global Custom Field to the Columns of the JQL result.
- Try to drag and drop the field to a different column in the JQL result.
- Export the JQL results in to a CSV file.
Expected Results
- While drag-dropping the Custom Field column - Jira should move the column in the UI.
- While exporting the JQL results as .csv file - Custom Field should display properly, with all the field values filled in the column.
Actual Results
- While drag-dropping the Custom Field column - the column disappears from the results.
- While exporting the JQL results as .csv file - duplicate field with the same field name is displayed in the .csv sheet.
Workaround
- Use New Issue Navigator, which does not have this problem: https://community.atlassian.com/t5/Jira-Software-articles/Introducing-the-new-issue-search-to-Jira-Cloud-users/ba-p/2276375
- 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.
- relates to
-
JRACLOUD-76466 Jira should store the custom field details based on field ID instead of the field name
- Closed
-
JSWCLOUD-18756 Restrict Team-Managed custom fields name if already exists another custom field with the same name
- Gathering Interest