-
Bug
-
Resolution: Duplicate
-
Medium
-
1
-
Minor
-
0
-
Issue Summary
Having 2 custom fields with same name(case insensitive) causes an issue in issue export in Team Managed Project
Steps to Reproduce
1) Create two TMP projects (Project A, Project B).
2) Create custom fields with the same name in each project.
3) Open the issue search screen and filter by Project A and make sure to include the custom field created for Project A and fill in value.
4) Export issues to CSV (user default settings).
5) In the exported CSV, the custom fields created in step 2 appear twice.
It is assumed that the custom fields from Project A and Project B are appearing. One of the field(from Project B) is blank.
6) Delete the custom fields created in step 2 from Project B.
7) Repeat steps 3 and 4.
8) The issue in step 5 is resolved, and only one custom field from Project A appears.
Example of data:
- Project A's custom field: TEST FIELD
- Project B's custom field: TEST FIELD
--> both fields get exported with one of them empty in the CSV.
Also reproducible:
- Project A's custom field: TEST FIELD
- Project B's custom field: TEST field
--> both fields get exported with one of them empty in the CSV.
Expected Results
In CSV, only the field from Project A should be exported, not both the fields.
Actual Results
Both fields from Project A and Project B are exported to CSV.
Workaround
Currently, there is no workaround.
- is cloned from
-
JRACLOUD-77176 having 2 custom fields with similar name, causes an issue in JQL columns and excel exporting
-
- Closed
-