-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
10.77, 10.78, 10.79
-
2
-
Severity 3 - Minor
-
No
Issue Summary
Custom Fields are missing when exporting Dependencies
Steps to Reproduce
- Set Tier1 filter options to a meaningful criteria
- Browse to Details Panels Settings page
- Select any Portfolio
- Select Dependency work item type
- Create a new or repurpose an existing Custom Field
- Activate the new field
- Click Save button to commit changes
- Browse to Dependencies grid
- Open any Dependency entry
- Locate the newly activated custom field and fill it with relevant data
- Click Save & Close to commit changes
- Click More Actions button, then select Export all Dependencies
- Notice the exportDependencies.xls file is downloaded
- Open the export file in Excel
- Notice the custom field column is missing
Expected Results
- The corresponding custom field column is present & populated in the export file, as it is with other work item types, e.g. risks.
Actual Results
- The custom field column is missing
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available.
- duplicates
-
JIRAALIGN-707 Export: Custom fields aren't exported for Objectives, Tasks, Risks and Test Cases
- Closed
-
JIRAALIGN-735 Custom Fields Don't Show On Dependency Grid
- Closed
- resolves
-
ALIGNSP-6019 Loading...
-
ALIGNSP-7939 Loading...
(2 resolves)