Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-66150

Values mapped to "Issue ID" field upon import will be saved to "External Issue ID" custom field

    XMLWordPrintable

Details

    • 7.02
    • 46
    • Severity 3 - Minor
    • 17
    • Hide
      Atlassian Update – 04 September 2023

      Dear Customers,

      Thank you for your report and feedback. The external system import module is designed to be stateful, which means the Issue ID values from the CSV file are saved to an "External Issue ID" custom field rather than being discarded after import. This design is to ensure data consistency and to allow future mapping from the source system.

      We understand that this can pose a challenge when performing new imports due to the difficulty in finding unique ID values. To address this, we have updated our documentation to highlight this stateful behavior during the import process. We hope this provides a clearer understanding of the process.

      We have also made improvements to our import system based on your feedback. Specifically, now when duplicated tickets are identified during the import process and therefore not imported, any duplicated ticket's subtasks are skipped as well. This change aims to prevent unwanted duplications and to maintain data integrity - e.g. subtask is imported, but parent is not. Changes will be released in Jira 9.13.

      We have also created a new feature suggestion ticket to address this issue more comprehensively. This ticket will allow us to consider potential improvements in our future development plans, such as the possible introduction of separate "Issue ID" and "External Issue ID" during the import process, as you suggested. Please refer to JRASERVER-76235.

      We appreciate your input as it helps us continually improve our systems and processes. Please don't hesitate to reach out if you have any further questions or suggestions.

      Kind regards,
      Grzegorz Kulinski
      Jira DC developer

      Show
      Atlassian Update – 04 September 2023 Dear Customers, Thank you for your report and feedback. The external system import module is designed to be stateful, which means the Issue ID values from the CSV file are saved to an "External Issue ID" custom field rather than being discarded after import. This design is to ensure data consistency and to allow future mapping from the source system. We understand that this can pose a challenge when performing new imports due to the difficulty in finding unique ID values. To address this, we have updated our documentation to highlight this stateful behavior during the import process. We hope this provides a clearer understanding of the process. We have also made improvements to our import system based on your feedback. Specifically, now when duplicated tickets are identified during the import process and therefore not imported, any duplicated ticket's subtasks are skipped as well. This change aims to prevent unwanted duplications and to maintain data integrity - e.g. subtask is imported, but parent is not. Changes will be released in Jira 9.13 . We have also created a new feature suggestion ticket to address this issue more comprehensively. This ticket will allow us to consider potential improvements in our future development plans, such as the possible introduction of separate "Issue ID" and "External Issue ID" during the import process, as you suggested. Please refer to JRASERVER-76235 . We appreciate your input as it helps us continually improve our systems and processes. Please don't hesitate to reach out if you have any further questions or suggestions. Kind regards, Grzegorz Kulinski Jira DC developer

    Description

      Expected Behavior

      Issues will be imported based on the ID specified in CSV file, which will be discarded after the import process is complete. This scenario is suggested when importing issues and subtasks on Importing data from CSV - Encapsulating JIRA data structure in your CSV file

      Actual Behavior

      The values to the Issue ID field during a CSV import are saved to an "External Issue ID" field. When performing new imports, they will usually not work properly because it's rather difficult to find unique ID values. We should have two different options upon import: "Issue ID" - a value that will only be used within that import process to link issues; and "External Issue ID" for when users want to map the ID that came from the source system.

      Steps to Reproduce

      Try to import a file containing the following data twice, mapping "id" to "Issue ID" and "parent id" to "Parent ID".

      id,parent id,summary
1,,"Test"
,1,"Test sub-task"

      The value set on "Issue ID" will be replicated to the "External Issue ID" value of the issue with summary "Test". Upon a new import, it will skip that issue and register the following on the import log:

      External issue 1 already exists as PROJ-1, not importing.

      Workaround

      Find a unique value to use in that field. You may use the below database query to make it easier.

      SELECT * FROM customfieldvalue WHERE customfield IN (SELECT id FROM customfield WHERE cfname = 'External issue ID');

      or delete the External issue ID field after each import.

      Attachments

        Issue Links

          followed by

          Suggestion - JRASERVER-76235 Enhancement of External System Import Functionality – Introduction of Stateless and Stateful Import Options

          • Gathering Interest
          relates to

          Suggestion - JRASERVER-64477 New "External issue ID" field is created on each import

          • Gathering Interest

          RAID-3171 Loading...

          was cloned as

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-81999 Values mapped to "Issue ID" field upon import will be saved to "External Issue ID" custom field

          • Medium - Medium priority issues
          • Gathering Impact
          mentioned in

          Page Loading...

          Page Loading...

          Activity

            People

              Unassigned Unassigned
              jpalharini Joao Palharini (Inactive)
              Votes:
              87 Vote for this issue
              Watchers:
              69 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: