Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-7604

As a user, when I import project using CSV importer, I want also to import the relationships from Epic-> Story

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • None
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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

            Przemyslaw Borkowski (Inactive) added a comment -

            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

            Przemyslaw Borkowski (Inactive) added a comment - 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

            MattS added a comment - - edited

            I think you can import Epics from CSV and provide values for Epic Name. Then in Stories later in the CSV use an Epic Link column with the name of the Epic that the Story should be part of. This was in one of the more recent releases of the CSV importer as I recall?

            Other comments around https://confluence.atlassian.com/display/JIRA/Importing+Data+from+CSV?focusedCommentId=720418765#comment-720418765
            about this

            MattS added a comment - - edited I think you can import Epics from CSV and provide values for Epic Name. Then in Stories later in the CSV use an Epic Link column with the name of the Epic that the Story should be part of. This was in one of the more recent releases of the CSV importer as I recall? Other comments around https://confluence.atlassian.com/display/JIRA/Importing+Data+from+CSV?focusedCommentId=720418765#comment-720418765 about this

            Win added a comment -

            Hi Atlassian, any updates on this?

            Win added a comment - Hi Atlassian, any updates on this?

            Brian K added a comment -

            there's this: https://ecosystem.atlassian.net/browse/JIM-988
            but I still don't have the Epic Link option when identifying the fields to map.

            Brian K added a comment - there's this: https://ecosystem.atlassian.net/browse/JIM-988 but I still don't have the Epic Link option when identifying the fields to map.

            HyperVelocity Sales added a comment -

            Lets do it!

            HyperVelocity Sales added a comment - Lets do it!

            JustinL added a comment -

            What's going on with this?

            JustinL added a comment - What's going on with this?

            Alex Zoro added a comment -

            Hi,

            I just hit this issue when trialling JIRA/Greenhopper. As on import you can specify the Story->Sub-task relationship, and the Epic->Story relationship is (it seems to me) the same, I was surprised to see the Epic->Story link fail on import. Fixing this would help import of significant projects a lot.

            Alex Zoro added a comment - Hi, I just hit this issue when trialling JIRA/Greenhopper. As on import you can specify the Story->Sub-task relationship, and the Epic->Story relationship is (it seems to me) the same, I was surprised to see the Epic->Story link fail on import. Fixing this would help import of significant projects a lot.

              Unassigned Unassigned
              oalsafi OmarA
              Votes:
              43 Vote for this issue
              Watchers:
              27 Start watching this issue

                Created:
                Updated:
                Resolved: