Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-8699

Status value is removed when we import data with Insight

XMLWordPrintable

      Issue Summary

      Attributes that has the type Status with a current status I.e "active" gets removed when we import data from an external source like a CSV, LDAP import for example.

      This affect Insight Version 8.5.2 and forward

      Steps to Reproduce

      1. Create an Object Type with a Status Attribute (no need to select statuses)
      2. Create a few Objects and make sure the Status Attribute is set to Active
        • You can also configure an Automation rule to set the Status to Active when an Object is created.
      3. Create a CSV file to import - so that New Objects will be created, and existing Objects will be "Missing Objects"
      4. Configure an Import (any, but easier with CSV) and map to your object type's Attributes, do not map the Status Attribute
      5. On the Object Type Mapping set:
        • Missing Object: Update
        • Attribute to edit: Status
        • New value of attribute to edit: Inactive
      6. Sync the import
      7. First time the import runs, all objects will be created. If we had create the automation rule in Step 3, those objects will have ''Status' = Active
      8. Update some attributes in the CSV for some objects and import again, so that some Objects will be updated

      Expected Results

      Updated objects should keep the Status = Active, and only affected attributes should be updated

      Actual Results

      'Status' attribute from the updated objects will be removed. All updated Objects will show "No Value" for Status attribute

      This does not happen when Missing Objects: Ignore 

      Workaround

      Add an automation rule:

      WHEN: object Updated IF: Status IS EMPTY THEN: Attribute Value: Status to Active

       

      NOTE:

      This happens to objects that are created within the UI, manually.

      Objects created within the CSV Import, then edited to be assigned a status - the status will remain.

          Form Name

            [JSDSERVER-8699] Status value is removed when we import data with Insight

            Tobias Meyer added a comment -

            Hello Atlassian Team...

            I investigated this behaviour and can share my insights with you: (https://www.youtube.com/watch?v=Ln1rDM8NrHQ)

            Steps to Reproduce

            1. Create a csv importer
            2. On the Object Type Mapping set:
              • Missing Object: Update
              • Attribute to edit: Any Attribute the type doesn't matter
              • New value of attribute to edit: Inactive
            3. Important: The attribute selected on Attribute to edit isn't available on the import or no mapping is defined!
            4. Run the import (synchronize)
            5. Modify one of the imported objects (change one attribute which is present on the import mapping) and set the attribute you defined above on the Attribute to edit configuration
            6. Run the import (synchronize) again

            Expected Results

            Only the mapped attributes should be updated and the Attribute to edit should only be updated if the object is missing in the CSV source!

            Actual Results

            The attribute value defined on the Attribute to edit configuration is removed!

            Possible Solutions

            1. Change the import behaviour to only set the Attribute to edit if the object is missing and not generally
            2. Allow a "hard coded" Input in the Object type mapping data locator on the import configurator (e.g. Data Locator = "Active", Assets Attribute = Status)

             

            Tobias Meyer added a comment - Hello Atlassian Team... I investigated this behaviour and can share my insights with you: ( https://www.youtube.com/watch?v=Ln1rDM8NrHQ) Steps to Reproduce Create a csv importer On the Object Type Mapping set: Missing Object:  Update Attribute to edit : Any Attribute the type doesn't matter New value of attribute to edit:  Inactive Important : The attribute selected on Attribute to edit isn't available on the import or no mapping is defined! Run the import (synchronize) Modify one of the imported objects (change one attribute which is present on the import mapping) and set the attribute you defined above on the Attribute to edit configuration Run the import (synchronize) again Expected Results Only the mapped attributes should be updated and the Attribute to edit should only be updated if the object is missing in the CSV source! Actual Results The attribute value defined on the Attribute to edit configuration is removed! Possible Solutions Change the import behaviour to only set the Attribute to edit if the object is missing and not generally Allow a "hard coded" Input in the Object type mapping data locator on the import configurator (e.g. Data Locator = "Active", Assets Attribute = Status)  

            Leonard K added a comment -

            Hi Atlassian,

            can you please proceed here to deliver a bugfix? This also affects our Jira instance with version 9.4.9. With every import and the workaround automation it will spam up the object history (import removes the status, then automation kicks in and set status to something --> with the next import the circle begins again)

            This is very confusing for our agents and not convenient.

            Leonard K added a comment - Hi Atlassian, can you please proceed here to deliver a bugfix? This also affects our Jira instance with version 9.4.9. With every import and the workaround automation it will spam up the object history (import removes the status, then automation kicks in and set status to something --> with the next import the circle begins again) This is very confusing for our agents and not convenient.

            Steven Behnke added a comment -

            please fix, this is hard to workaround as your workaround only handles situations where the status value didn't matter.

            Steven Behnke added a comment - please fix, this is hard to workaround as your workaround only handles situations where the status value didn't matter.

            Andreas Krupp (catworkx) added a comment -

            Hello Team,

            Any update on this? It would be great if you would look into this, because "deleting" data that is not supposed to be deleted is hardly a "minor" problem.

            Best regards and thx!

            Andreas

            Andreas Krupp (catworkx) added a comment - Hello Team, Any update on this? It would be great if you would look into this, because "deleting" data that is not supposed to be deleted is hardly a "minor" problem. Best regards and thx! Andreas

              4efd9de64ab4 Mingyi Yang
              1e8559fc3c14 Thomas Grahn
              Affected customers:
              16 This affects my team
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: