-
Bug
-
Resolution: Fixed
-
High
-
19
-
Minor
-
49
-
Issue Summary
When running External Imports to import Assets Objects, if an Object has a User Attribute added manually, separately from the External Import, then when the External Import tries to update the Object for unrelated Attributes, it will fail with an error that the User Attribute's value doesn't exist in Jira.
Steps to Reproduce
- Enable External Import
- Push Object mappings
- Manually add an attribute of type User to the Object Type via the User Interface - Leave the User Attribute Empty
- Run the import (this will run successfully)
- Add a value to the previously created User Attribute on the Object Type
- Manually update an object, changing any other attribute that is present in the import mapping
- Re-run the import, the import will identify that 1 object needs to be updated
Expected Results
The Object will be updated with the non-User Attribute Values.
Actual Results
The import will fail to update the object due to the User attribute.
Example of the error:
Error: User(s) (<AtlassianAccountID>) not found in Jira. [Object (Label: <object-label>, Id: <object-id>)].
Workaround
Create a User Object that has the User Attribute to go in place of the User on relevant Objects via an Object Attribute. i.e. create a layer of abstraction between the Object that needs to be linked to the User and the User.
For example, instead of having a Workstation Object with a User Attribute of Owner, have the Owner Attribute be an Object Attribute that links to a static User Object.
This User Object doesn't need to be updated, typically, so it won't affect External Imports trying to update Assets Object Attributes, but it will have a User Attribute that links to the User's actual Atlassian Account.
- is caused by
-
JSDCLOUD-11178 Assets external / Discovery import to run as the generator of the OAuth token
- Gathering Interest
-
- Reviewing
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
[JSDCLOUD-12410] Using Assets External Imports to try and update an Object with a User Attribute will fail despite the User Attribute not being related to the External Import
Just adding my vote here as this bug as advised by Atlassian support seems to be responsible for us now getting import errors constantly, I add here the correspondence I received from Atlassian support:
Yes I have been able to see the errors on the import history for the import configuration and I've been doing some investigations on these errors.
Looking into the 'unauthenticated' errors shown on the error logs, it looks like the Add support to User type attributes on External Import bug was responsible for these errors. The process Insight goes through when an Attribute is updated is to verify all Attributes when any are updated.
So, even if an unrelated Attribute is being updated via External System Import, if the Jira account Attribute (In this case, the 'Owner' attribute) has a value, it will return an error and not process the updates since that value cannot be verified – looking into the objects that were referred to by the error messages, they all have the 'Owner' attribute filled in
REDACTED LINKS
I'm afraid the best workaround that can be provided until this bug is fixed would be the following:
#
#Set Jira account Attribute (Owner) Values to empty/null via a different method for the objects that need updates.
Perform the Discovery import again
I don't think these workarounds are acceptable for a system that is designed to be an "Asset management system" and this bug needs to be addressed.
This bug is related to https://jira.atlassian.com/browse/JSDCLOUD-10732 which has 101 votes
Quick update: A fix has been rolled out. External Import can now update the object for unrelated attributes even if the object has an User attribute added manually.