-
Bug
-
Resolution: Fixed
-
High
-
17
-
Severity 2 - Major
-
84
-
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.
Summary
Epic Link is not correctly set on issues imported through CSV.
Environment
- JIRA v1000.253.1
Steps to Reproduce
- Create an Epic
Epic name: Epic1
- Import issues through CSV
Summary,Epic Link Test issue, Epic1
Expected Results
Issue imported should have an Epic linked
Actual Results
The import is done without errors but Epic link field is blank
Notes
Partial Workaround
If you don't have many epics, you can bulk edit the issue, one search per epic. For example, if you have these epics with these stories:
- Epic: ABC-1: Epic Name: My Epic 1
- Story in Epic ABC-1: ABC-2, Epic Link: My Epic 1
- Story in Epic ABC-1: ABC-3, Epic Link: My Epic 1
- Epic ABC-4: Epic Name: My Epic 2
- Story in Epic ABC-4: ABC-5, Epic Link: My Epic 2
It's possible to:
- Import the 'Epic Name' to 'Epic Name', as expected
- Create a new text field (My Epic Link)
- Import 'Epic Link' to this text field (My Epic Link)
- For each Epic, search for stories with the Epic Link, for example
'My Epic Link' = 'My Epic 1'
- Bulk edit it to change the 'Epic Link' to 'My Epic 1'
- is related to
-
JRASERVER-62251 Import epic link through CSV is no longer working
- Closed