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

CSV importer doesn't import "Select List (cascading)" field data correctly.

      Issue Summary

      CSV importer doesn't import Select List (cascading) field data correctly.
      This problem happens only when we use Issues > Import Issues from CSV on the top page.
      This problem never happens when we import CSV using System > External System Import in the Administration page.

      Steps to Reproduce

      1. Create a project
      2. Add Select List (cascading) custom field and set their options
      3. Associate the custom field to the project you created on step1
      4. Import CSV from Issues > Import Issues from CSV

      Expected Results

      The CSV data should be imported to JIRA correctly.

      Actual Results

      Select List (cascading) custom field data (especially the child option) was not imported.
      See the screenshot attached: Select List (cascading) CSV import failed.png

      Workaround

      Use System > External System Import in Administration page instead.

            [JRACLOUD-81994] CSV importer doesn't import "Select List (cascading)" field data correctly.

            Atlassian Update - January 2024

            After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-81924 – Cascading Custom Field not imported correctly from CSV import which has more votes.

            We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - January 2024 After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-81924 – Cascading Custom Field not imported correctly from CSV import which has more votes. We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Hello!

            We’re looking to improve the import experience in Jira and are keen to understand how our community is using the Jira Import Module (JIM). If you’ve used JIM to migrate/move data into Jira recently, we’d love to hear about your experience. Please take a few minutes to fill out this survey. Your feedback will help us learn how we can improve your experience in importing data.

            Survey link - https://forms.gle/NYNkmS92r96z42QV9

            Thanks!

            Prashanth M
            Product Manager, Jira Platform

            Prashanth M added a comment - Hello! We’re looking to improve the import experience in Jira and are keen to understand how our community is using the Jira Import Module (JIM). If you’ve used JIM to migrate/move data into Jira recently, we’d love to hear about your experience. Please take a few minutes to  fill out this survey . Your feedback will help us learn how we can improve your experience in importing data. Survey link -  https://forms.gle/NYNkmS92r96z42QV9 Thanks! Prashanth M Product Manager, Jira Platform

            This is a significant bug that prevents Project admin from importing issues where a cascading selection list needs to be set.  The only work around is that the import must be done by a jira-admin adding significant overhead to companies.

            Todd Alden added a comment - This is a significant bug that prevents Project admin from importing issues where a cascading selection list needs to be set.  The only work around is that the import must be done by a jira-admin adding significant overhead to companies.

              Unassigned Unassigned
              aguedespinto Aline
              Affected customers:
              5 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: