Assets Discovery import error 'rlabs.insight.i18n.constraint.violation.ObjectAttributeValueBean.NotFound.Users' is shown on Jira Cloud if an object has a manually assigned User value for a manually added User type attribute

Issue Summary

Assets Discovery import error 'rlabs.insight.i18n.constraint.violation.ObjectAttributeValueBean.NotFound.Users' is shown on Jira Cloud if an object has a manually assigned User value for a manually added User type attribute

This is reproducible on Data Center: no

Steps to Reproduce

1. Set up an export from Assets Discovery to Jira Cloud as per Export data from Asset Discovery to Assets Cloud.
2. Run an Assets Discovery scan and verify that the export to Jira Cloud is working as expected.
3. On Jira Cloud, edit the Host object type to add an User type attribute.
   
4. Edit at least one of the imported Host objects, assign a value (Jira user) to the newly created attribute.
5. Run another Assets Discovery scan and check the result.

Expected Results

The export from Assets Discovery to Jira Cloud is done without any error on either sides

Actual Results

• An import error about the User type attribute we manually created is shown on Jira Cloud.

  context: rlabs-insight-attribute-690; messages: [ErrorMessage{i18nKey='rlabs.insight.i18n.constraint.violation.ObjectAttributeValueBean.NotFound.Users'
  

  

• This error appears for every object that has a value for the User type attribute we added manually. If we remove the value of this attribute from all objects before another import from Assets Discovery, this error will not appear.
  

• This issue is only reproducible on Jira Cloud

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available