Problem Statement

After upgrading my Device42 integration plugin to version 1.2.15, some Objects in the Assets Object Schema are missing data for specific attributes, like not having all the IP addresses from the object in Device42.

As a result, the object differ from Assets to Device42 and are not able to be fully integrated with JSM.

Issue Summary

Some customers have objects in Device42 with a large sum of attribute-data, such as objects having a high number of IP addresses. When trying to run the import to Jira via the Device42 integration plugin, some of this data is missing for a given object.

When viewing the data from the Assets Object Schema, and comparing it to what is in Device42, there are distinct differences but there are no errors present in the log files.

This seems to impact version 1.2.15 of the Device42 Integration Plugin

Replication Steps:

Atlassian Support has not been able to replicate this issue, however, our support teams have worked closely with impacted customers to help understand the steps, and results, to correct the behavior

1. As a Jira Administrator, setup a Device42 Integration with JSM's Assets
2. Verify that the data collected mirrors our expectations, here
3. Compare the results in the Assets Object Schema to the same device in Device42

Expected Results: The data from Device42 matches the data in the Asset Object, perfectly
Observed Results: In specific situations, customers noticed that IP addresses, or other meta data, did not match between Asset Objects and Device42

Workaround

This issue has been identified as an API issue between Jira and Device42 which only impacts version 1.2.15 of the plugin. To resolve this issue, contact Atlassian Support so that the issue can be verified on your environment and we can provide accurate next steps.