Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-10045

Import duplication when object type mapping has two identifiers and one is another referenced object

      Issue Summary

      During object import, objects are duplicated when object type mapping has two identifiers and one is another referenced object

      Steps to Reproduce

      1. Create object type called "City" in your schema (with just default attributes) 
      2. Also create an object type called "Employee" with the default attributes and an attribute of "City" of the City object type created in step 1
      3. Create an import configuration in your schema with the attached CSV file
      4. After the configuration is created, create an object type mapping within the configuration selecting the Employee object type created in step 2 and set the identifiers of the mapping to be "Name" and "City" and ensure both are ticked (See screenshot for end result of import configuration)
        1. Ensure that for the Employee object type mapping, Missing objects are ignored
      5. Execute import and check that the objects were correctly imported
      6. Execute import another time without making any changes

      Expected Results

      We should see no duplicates

      Actual Results

       

      We see duplicates of all the objects

       

      Workaround

      This seems to only happen if you use "Label" in the import AQL of the referenced object. Using the attribute name instead can fix this. For example:

      • Name = ${Placeholder}

            [JSDCLOUD-10045] Import duplication when object type mapping has two identifiers and one is another referenced object

            Nicole added a comment -
            Atlassian Update - July 1, 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 Service Management Cloud 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 via raising a ticket at https://support.atlassian.com.

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

            Nicole added a comment - Atlassian Update - July 1, 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 Service Management Cloud 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 via raising a ticket at https://support.atlassian.com . Thank you again for providing valuable feedback to our team! Jira Service Management Cloud team

            Tim added a comment -

            Please understand that I am unable to use the Update missing object on Import feature. This is important because I want to update the employee status to Inactive if missing from the CSV. 

            I end up with the original objects and the updated objects.  According to the bug fix policy I would expect this to be a P2 or a minimum P3.

            This issue clearly impacts any customer using this product and am hopeful a short term resolution.

            -tim

            Tim added a comment - Please understand that I am unable to use the Update missing object on Import feature. This is important because I want to update the employee status to Inactive if missing from the CSV.  I end up with the original objects and the updated objects.  According to the bug fix policy I would expect this to be a P2 or a minimum P3. This issue clearly impacts any customer using this product and am hopeful a short term resolution. -tim

              8f5df932eda6 Dorothea Linneweber
              d80a14de5ac6 Kalanika Weerasinghe
              Affected customers:
              10 This affects my team
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: