We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-71550

Importing Epics, Epic Links and linked tickets cannot be done using single CSV file

      Issue Summary

      Importing Epics, Epic Links and linked tickets cannot be done using single CSV file. Two or more CSVs are required to import new issues and Epics and to link them.

      Steps to Reproduce

      1. Prepare a CSV file that contains new Epics, new or existing issues and Epic Links to link those two
      2. Import the data using Importer functionality

      Expected Results

      Epics and corresponding issues are created and linked from the same CSV file.

      Actual Results

      Links are not created after the import.

      The below exception is thrown in the atlassian-jira.log file:

      2016-05-25 19:17:57,822 WARN - Cannot add value [ [My Epic] ] to CustomField Epic Link in Issue with summary 'Story in Epic'. Probably value was in incorrect format
      

      Workaround

      The workaround is described on the knowledge article Cannot Import Epic Link from CSV due to Incorrect Format.

      The idea is to:

      • Use one CSV file to import new Epics and issues
      • Use the second CSV file to import links between Epics and issues.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-71550

            Importing Epics, Epic Links and linked tickets cannot be done using single CSV file

              • Icon: Bug Bug
              • Resolution: Unresolved
              • Icon: Low Low
              • None
              • 7.13.5, 8.5.5, 8.20.10
              • Jira Importers Plugin

                Issue Summary

                Importing Epics, Epic Links and linked tickets cannot be done using single CSV file. Two or more CSVs are required to import new issues and Epics and to link them.

                Steps to Reproduce

                1. Prepare a CSV file that contains new Epics, new or existing issues and Epic Links to link those two
                2. Import the data using Importer functionality

                Expected Results

                Epics and corresponding issues are created and linked from the same CSV file.

                Actual Results

                Links are not created after the import.

                The below exception is thrown in the atlassian-jira.log file:

                2016-05-25 19:17:57,822 WARN - Cannot add value [ [My Epic] ] to CustomField Epic Link in Issue with summary 'Story in Epic'. Probably value was in incorrect format
                

                Workaround

                The workaround is described on the knowledge article Cannot Import Epic Link from CSV due to Incorrect Format.

                The idea is to:

                • Use one CSV file to import new Epics and issues
                • Use the second CSV file to import links between Epics and issues.

                        Unassigned Unassigned
                        mfilipan Marko Filipan
                        Votes:
                        4 Vote for this issue
                        Watchers:
                        5 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            mfilipan Marko Filipan
                            Affected customers:
                            4 This affects my team
                            Watchers:
                            5 Start watching this issue

                              Created:
                              Updated: