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

The non-admin CSV Importer "Validate" feature returns a false error when importing Parent/Sub-task issues

XMLWordPrintable

      Summary

      When using the non-admin CSV import tool, the "Validate" feature is giving a false error when validating a CSV with Parent/Sub-task. Clicking on "Begin Import" with the same CSV and configuration will import the issues successfully with no errors.

      Environment

      • Atlassian Cloud

      Steps to Reproduce

      1. Go to the non-admin CSV importer by going to the Issue Navigator, and clicking on the "..." on the top right -> Import issues from CSV
      2. Use this file Test-Link.csv which contains this: 
        Summary, Issue Type, Issue ID, Parent ID
First Issue, Task, 1,
Second Issue, Sub-Task, , 1
      1. Select any project, leave the other settings as default.
      2. Map the CSV fields accordingly. (Summary:Summary, Issue Type:Issue Type, Parent ID:Parent Id, Issue ID:Issue Id)
      3. On the page with the "Begin Import" and "Validate" buttons, click on "Validate".

      Expected Results

      The Validation should pass through successfully without any errors.

      Actual Results

      The validation returns this error:

      The validation process has found 1 error/s
- Fatal error during import: Parent Issue cannot be null

      Notes

      • Although the Validation returns an error, the import will be successful if the user clicks on the "Begin Import" button.
      • Even when using the example CSV file for Sub-tasks provided in the documentation, the same error is returned when validating.

      Here are the Validation logs:

      2018-01-05 13:09:11,873 INFO - Importer started!
2018-01-05 13:09:11,880 INFO - Engine is running in Validation-only mode
2018-01-05 13:09:12,089 INFO - All issues will be imported to project: Monopoly (MON)
2018-01-05 13:09:12,105 INFO - Creating issue: [externalId='1', summary='First Issue']
2018-01-05 13:09:12,226 INFO - No problems found with issue 'First Issue'
2018-01-05 13:09:12,232 INFO - Creating issue: [externalId='autoid-8287858083947989194', summary='Second Issue']
2018-01-05 13:09:12,238 ERROR - Fatal error during import: Parent Issue cannot be null

      Here are the logs when the file is actually imported (without making any changes):

      2018-01-05 10:03:22,732 INFO - Importer started!
2018-01-05 10:03:22,740 INFO - Engine is running in Import mode
2018-01-05 10:03:22,951 INFO - All issues will be imported to project: Monopoly (MON)
2018-01-05 10:03:22,968 INFO - Creating issue: [externalId='1', summary='First Issue']
2018-01-05 10:03:25,406 INFO - Issue created successfully with Key [MON-15], [externalId='1', summary='First Issue']
2018-01-05 10:03:25,701 INFO - Creating issue: [externalId='autoid-2380441573030003319', summary='Second Issue']
2018-01-05 10:03:27,097 INFO - Issue created successfully with Key [MON-16], [externalId='autoid-2380441573030003319', summary='Second Issue']

      Workaround

      None.

        1. Test-Link.csv
          0.1 kB

            [JRACLOUD-81974] The non-admin CSV Importer "Validate" feature returns a false error when importing Parent/Sub-task issues

            Rohit Verma (Inactive) added a comment -

            Rolled out in prod

            Rohit Verma (Inactive) added a comment - Rolled out in prod

            Rohit Verma (Inactive) added a comment -

            Rolled out to production at the provided schedule 2024-01-11T05:30:00.000Z 

            Rohit Verma (Inactive) added a comment - Rolled out to production at the provided schedule 2024-01-11T05:30:00.000Z 

            Rohit Verma (Inactive) added a comment -

            Fix for this has merged and rolled out to hello. Scheduled to rollout in production tomorrow 2024-01-11T05:30:00.000Z 

            Rohit Verma (Inactive) added a comment - Fix for this has merged and rolled out to hello. Scheduled to rollout in production tomorrow 2024-01-11T05:30:00.000Z 

            Aathif Nihas added a comment -

            The above issue is still happening even after 11/24/2023. Just ignoring the exception imports succesfully

            Aathif Nihas added a comment - The above issue is still happening even after 11/24/2023. Just ignoring the exception imports succesfully

            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

            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

            NiYunfan added a comment -

            It's nightmare for user to troubleshooting/modify csv contents... and eventually found it's a validation bug. time wasted.

            Please fix the bug to save life. Thanks!

            NiYunfan added a comment - It's nightmare for user to troubleshooting/modify csv contents... and eventually found it's a validation bug. time wasted. Please fix the bug to save life. Thanks!

            Erin Ennis added a comment -

            Thankful for Google & finding this ticket to save me hours of debugging. Still a bug, confirmed that just blowing by the Validation created issues as expected.

            Erin Ennis added a comment - Thankful for Google & finding this ticket to save me hours of debugging. Still a bug, confirmed that just blowing by the Validation created issues as expected.

            Sammy Scruggs added a comment -

            This bug is still an issue. I got so tired of trying to resolve the issue that I just went ahead with the import to see what would happen. To my surprise everything worked correctly. This issue is purely happening with the Validate step, and will not actually error out when you run the import. This should be a simple fix for Atlassian. I am not sure why it has yet to be resolved.

            Sammy Scruggs added a comment - This bug is still an issue. I got so tired of trying to resolve the issue that I just went ahead with the import to see what would happen. To my surprise everything worked correctly. This issue is purely happening with the Validate step, and will not actually error out when you run the import. This should be a simple fix for Atlassian. I am not sure why it has yet to be resolved.

            paolo vigorito added a comment -

            Still happening, any work around found?

            paolo vigorito added a comment - Still happening, any work around found?

            Mykenna Cepek added a comment -

            This seems to be related to https://jira.atlassian.com/browse/MIG-379

            Mykenna Cepek added a comment - This seems to be related to  https://jira.atlassian.com/browse/MIG-379

              75175a3526d9 Rohit Verma (Inactive)
              msatriya Sadiq (Inactive)
              Affected customers:
              30 This affects my team
              Watchers:
              31 Start watching this issue

                Created:
                Updated:
                Resolved: