-
Bug
-
Resolution: Fixed
-
High
-
42
-
Severity 2 - Major
-
23
-
Summary
When a CSV export includes a cascading select list field, the field value shows incorrect value.
Also, if you add a custom field (select list cascading) in the Card Layout of your kanban board the value is different from the value shown in the issue view (and the value is the same as if you export csv).
Steps to Reproduce
- Create a cascading select list with multiple values for both parent and child values.
- Create an issue and select a value for the fields in both parent and child.
- Navigate to the issue navigator and find the issue created. Select the cascading field as a column for the search.
- Export to CSV (current fields).
Expected Results
The CSV export shows the same value as what is found in the issue.
Actual Results
The CSV export shows a different value although the value stored in the database is correct.
Notes
The value saved in database is correct and HTML export shows the correct value.
Workaround
- Export the search as HTML and change the file type to .xls/.xlsx from the .html format
- Contact Atlassian Support so they can apply a fix for the export issue.
No workaround for the Card Layout problem at the moment.
- causes
-
JSWCLOUD-16730 Custom field type Cascade selector child not working properly on boards
-
- Closed
-
- duplicates
-
JRACLOUD-69143 Cascading field is exporting wrong values when exporting issues to CSV
-
- Closed
-
- is blocked by
-
JSWCLOUD-16896 Cascading custom field is not displaying the correct information on card layout at the board.
-
- Closed
-
- is duplicated by
-
JRACLOUD-69206 CSV Export incorrect values from Select List (Cascading) field
-
- Closed
-
- relates to
-
JSWCLOUD-16896 Cascading custom field is not displaying the correct information on card layout at the board.
-
- Closed
-
-
NEXT-5741 Loading...
- is caused by
-
FD-2288 Loading...