-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
None
-
None
-
Severity 3 - Minor
Issue Summary
Exporting issues using the 'Open in Microsoft Excel' feature does not export Team-managed custom fields values.
Steps to Reproduce
- Create the same custom field name in more than one Team Managed project
- Search for issues from team-managed projects that have custom fields created and populated.
- Export the issues using the 'Open in Microsoft Excel' feature.
- Custom fields from the Team-managed project will be empty and lack data.
Expected Results
Excel file should contain Team-managed custom field data.
Actual Results
Excel file does not contain Team-managed custom field data.
Workaround
Export issues using Export Excel CSV (All fields)/(Current field) feature.
Or
From Google sheet Get issues from Jira and select the correct custom field
- duplicates
-
API-299 Custom Fields with same names in team-managed projects not populating data when exporting
-
- Gathering Impact
-
[API-488] Exporting issues using 'Open in Microsoft Excel' feature does not export Team-managed custom fields values
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
Attachment | New: workaround in google sheet.mov [ 416569 ] |
Attachment | New: Data retrieved for the correct custom field.png [ 416568 ] |
Attachment | Original: workaround.mov [ 416567 ] |
Description |
Original:
h3. Issue Summary
Exporting issues using the 'Open in Microsoft Excel' feature does not export Team-managed custom fields values. !screenshot-1.png|thumbnail! h3. Steps to Reproduce # Search for issues from team-managed projects that have custom fields created and populated. # Export the issues using the 'Open in Microsoft Excel' feature. # Custom fields from the Team-managed project will be empty and lack data. h3. Expected Results Excel file should contain Team-managed custom field data. h3. Actual Results Excel file does not contain Team-managed custom field data. h3. Workaround Export issues using *Export Excel CSV (All fields)/(Current field)* feature. |
New:
h3. Issue Summary
Exporting issues using the 'Open in Microsoft Excel' feature does not export Team-managed custom fields values. !screenshot-1.png|thumbnail! h3. Steps to Reproduce # Create the same custom field name in more than one Team Managed project # Search for issues from team-managed projects that have custom fields created and populated. # Export the issues using the 'Open in Microsoft Excel' feature. # Custom fields from the Team-managed project will be empty and lack data. h3. Expected Results Excel file should contain Team-managed custom field data. h3. Actual Results Excel file does not contain Team-managed custom field data. h3. Workaround Export issues using *Export Excel CSV (All fields)/(Current field)* feature. Or From Google sheet *Get issues from Jira* and select the correct custom field |
Attachment | New: workaround.mov [ 416567 ] |
Attachment | New: How to reproducce the problem.mov [ 416566 ] |
Closing this as duplicate. Please follow updates here https://jira.atlassian.com/browse/API-299