Assets CSV Import fails if attribute with type user is imported
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
In this article we are going to discuss a scenario in which a CSV Import for Assets fails to import new data or update existing data when attribute of type User is configured. Following error message appears in the log
2023-04-28 09:17:02,807 [insight-InsightImportThreadGroup-worker-thread-0] | Failed to update missing references on object xxxxxx (TEST-1234) due to ValidationInsightException: Validation errors were found: rlabs-insight-attribute-619:
ErrorMessage{i18nKey='rlabs.insight.i18n.constraint.violation.ObjectAttributeValueBean.NotFound.Users', parameters=\[user1], additionalMessage=null};If user attribute is not mapped in the import, the import of new data is possible but existing data is still not updated.
Environment
JSM 5.x
Cause
While importing csv validation is being done on the users. The checks are as follows:
- Retrieve user by key from cache falling back to Jira's UserManager
- Retrieve the logged in user (this will be the user running the import)
- Check that user has browse permissions
Browse permission can be managed global as well. More details here Managing global permissions.
Solution
If user's group is not set in Browse Users permission then add that group for Browse Users permission or set that user who is importing csv in one of the group having Browse Users permissions.
Document Add a user to a group should help to add user to group.