-
Suggestion
-
Resolution: Fixed
-
None
-
None
Per summary, in order to import this relationship, Epic Link has to be enabled under CSV fields mappings (Step 2). So will be more feasible if this field is visible there as well, so the users can import the parent Epic ID to this field.
[JSWCLOUD-7604] As a user, when I import project using CSV importer, I want also to import the relationships from Epic-> Story
Workflow | Original: JAC Suggestion Workflow JSWCLOUD [ 4099744 ] | New: JAC Suggestion Workflow 3 [ 4371447 ] |
Workflow | Original: JAC Suggestion Workflow 3 [ 3699630 ] | New: JAC Suggestion Workflow JSWCLOUD [ 4099744 ] |
Workflow | Original: JAC Suggestion Workflow [ 3470879 ] | New: JAC Suggestion Workflow 3 [ 3699630 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2315914 ] | New: JAC Suggestion Workflow [ 3470879 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2037443 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2315914 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2025723 ] | New: JIRA PM Feature Request Workflow v2 [ 2037443 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 1886148 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2025723 ] |
Project Import | New: Sun Apr 02 01:01:23 UTC 2017 [ 1491094883663 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Thanks matt.doar, for pointing me to this issue.
Yes, this scenario is 100% supported on JIM side. In my opinion this issue can be Closed.
CC: ohernandez@atlassian.com