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

            [JRACLOUD-82756] CSV imports does not map Issue types for Team managed projects

            Thank you very much for doing nothing about this low priority bug.  Why don't you just confess that Nextgen projects are just a marketing feature and there is next to no testing to ensure thaey work as specified.  I created a custom issue type to receive this data and now there is a bug that was acknowledged as high priority and then deprecated.  How many support articles suggest "Create a classic project and move ...".  How can this be a feature request, it is clearly a BUG.  Your documentation states clearly that this is possible in multiple places and yet it is a feature request.  Bring on the replacement for Atlassian.

            garth.mcdonald added a comment - Thank you very much for doing nothing about this low priority bug.  Why don't you just confess that Nextgen projects are just a marketing feature and there is next to no testing to ensure thaey work as specified.  I created a custom issue type to receive this data and now there is a bug that was acknowledged as high priority and then deprecated.  How many support articles suggest "Create a classic project and move ...".  How can this be a feature request, it is clearly a BUG.  Your documentation states clearly that this is possible in multiple places and yet it is a feature request.  Bring on the replacement for Atlassian.

            vanyukov added a comment -

            From a high priority bug this went to a low priority suggestion :facepalm:

            vanyukov added a comment - From a high priority bug this went to a low priority suggestion :facepalm:

            Belto added a comment - - edited

            Dear Customers,

            Since the current CSV import capabilities, were built to support Classic projects. We will take Next-gen support in CSV import as a feature request/suggestion and prioritize among other enhancements on our roadmap in the future.

            Cheers,

            Belto
            Cloud Support Engineer | Amsterdam

            Belto added a comment - - edited Dear Customers, Since the current CSV import capabilities, were built to support Classic projects. We will take Next-gen support in CSV import as a feature request/suggestion and prioritize among other enhancements on our roadmap in the future. Cheers, Belto Cloud Support Engineer | Amsterdam

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

                Created:
                Updated: