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.
Jira Platform CloudProject Type: software

Jira Platform Cloud

Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-82756

CSV imports does not map Issue types for Team managed projects

XMLWordPrintable

    • 2
    • 31

    • 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.

      Issue Summary

      When trying to import Issues via CSV into Next-gen Projects in Jira, the CSV importer fails to assign the Issues to the defined Issue Types and assigns it to a default Story/Task Issue Type.

      Environment

      • Team managed Project
      • External System Import

      Steps to Reproduce

      1. Prepare a CSV file with the Issue Type header with defined values (Epic, Bug, Custom,...)
      2. Import the CSV file into a Next-gen Project
      3. In the field mapping step, map the Issue Type field to their respective Issue Types

      Expected Results

      • Issues are created as the defined Issue Types from the file (Epic, Bug, Custom,...)

      Actual Results

      All of the Issues are created as a Story or Task Issue Type (varies per Project).

      Workaround

      1. Import the CSV file into a Company Managed Project instead
      2. Move the issues from the Company Managed Project to the Team Managed Project

      Migrate between team-managed and company-managed projects

        1. Screen Shot 2019-07-30 at 12.06.39 pm.png
          14 kB
          Alex Huang
        2. import_user_test.csv
          0.3 kB
          Belto

            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 Platform Cloud'
            1. Jira Platform Cloud
            2. JRACLOUD-82756

            CSV imports does not map Issue types for Team managed projects

            XMLWordPrintable

              • 2
              • 31

              • 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.

                Issue Summary

                When trying to import Issues via CSV into Next-gen Projects in Jira, the CSV importer fails to assign the Issues to the defined Issue Types and assigns it to a default Story/Task Issue Type.

                Environment

                • Team managed Project
                • External System Import

                Steps to Reproduce

                1. Prepare a CSV file with the Issue Type header with defined values (Epic, Bug, Custom,...)
                2. Import the CSV file into a Next-gen Project
                3. In the field mapping step, map the Issue Type field to their respective Issue Types

                Expected Results

                • Issues are created as the defined Issue Types from the file (Epic, Bug, Custom,...)

                Actual Results

                All of the Issues are created as a Story or Task Issue Type (varies per Project).

                Workaround

                1. Import the CSV file into a Company Managed Project instead
                2. Move the issues from the Company Managed Project to the Team Managed Project

                Migrate between team-managed and company-managed projects

                  1. Screen Shot 2019-07-30 at 12.06.39 pm.png
                    14 kB
                    Alex Huang
                  2. import_user_test.csv
                    0.3 kB
                    Belto

                        Unassigned Unassigned
                        lellis2@atlassian.com Belto
                        Votes:
                        52 Vote for this issue
                        Watchers:
                        47 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            lellis2@atlassian.com Belto
                            Votes:
                            52 Vote for this issue
                            Watchers:
                            47 Start watching this issue

                              Created:
                              Updated: