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

Can't use issue id for issue link when importing .csv

XMLWordPrintable

      Issue Summary

      Can't use issue id for issue link when importing .csv

      Steps to Reproduce

      1. Go to External System Import and chose .csv
      2. Have a .csv mapping issue links with issue ids instead of issue keys
      3. Start the import

      Expected Results

      Links are created correctly

      Actual Results

      Issues links are not created during the import, and the following error will be shown

      2021-03-05 20:44:14,943 INFO - Only new items will be imported
2021-03-05 20:44:15,068 INFO - Importing issue: [externalId='autoid--8904706533663185884', summary='s']
2021-03-05 20:44:15,445 INFO - 1 issues successfully created
2021-03-05 20:44:15,449 INFO - ------------------------------
2021-03-05 20:44:15,449 INFO - Finished Importing : Issues
2021-03-05 20:44:15,449 INFO - ------------------------------
2021-03-05 20:44:15,511 INFO - ------------------------------
2021-03-05 20:44:15,512 INFO - Importing: Issue Links & Subtasks
2021-03-05 20:44:15,512 INFO - ------------------------------
2021-03-05 20:44:15,512 INFO - Only new items will be imported
2021-03-05 20:44:15,518 ERROR - Unable to link issue from autoid--8904706533663185884 to 11857 with link named 'Blocks': Cannot find imported issue key for external id '11857'

      Workaround

      Have your .csv populated with the keys instead of ids

            [JRACLOUD-76145] Can't use issue id for issue link when importing .csv

            Genting Malaysia Berhad added a comment -

            Looking for a fix for this

            Genting Malaysia Berhad added a comment - Looking for a fix for this

            Matthew Hunter added a comment -
            Atlassian Update - May 9, 2022

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - May 9, 2022 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              asantos2@atlassian.com Augusto Pasqualotto (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: