-
Bug
-
Resolution: Fixed
-
High
-
6.4, Archived Jira Cloud
-
6.04
-
21
-
Severity 2 - Major
-
34
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Summary
Epic Link is not correctly set on issues imported through CSV.
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
-
JSWSERVER-11513 Include the issue key of the epic when exporting the Epic Link field in issue search results
- Closed
-
JSWSERVER-15878 Better handle Epic Name, Epic Link, and issue exports to HTML/CSV
- Gathering Interest
- relates to
-
JRACLOUD-62251 Import epic link through CSV is no longer working
- Closed
- caused by
-
SW-5001 Loading...
- mentioned in
-
Page Loading...
- was cloned as
-
JSB-174 Loading...