Assets - how to set a default value with Azure import

Question

While our Azure import into Assets works where the a name/description exists in Azure, if there is no data in the name/description field then the import fails, resulting in a missing object in our CMDB.

I have the Object Scheme Manager and Developer roles.

How can I set a default value (e.g. "Name required") when importing from Azure? We can't be the only people that have had this issue, so I'm hoping someone can share the best approach.

This page hints at a way, but I don't see the Automation tab it mentions. That said, this may only work after import, and so if the import fails it may not be the fix for our scenario anyway. https://confluence.atlassian.com/servicemanagementserver/configuring-assets-automation-rules-1044784502.html

Dave Furlani_2zy3uu · Answer

Thanks for directing me to the right KB page. From a read of that I've been able to see the settings related to the import (Edit object type mapping). And the page says that the treatment of empty and unknown values can be set to Use default, which we have. So far, so good.

The KB page says I can set a default value on the “Define import structure” screen for this object type... but I can find where that is, or at least not a UI that suggests I can set defaults. To the right of the Azure section the kebab menu offers "Edit import structure", but that form only has 2 fields (Name and Description) for the import.

After some more reading and a long chat with the support AI it looks like I need to log a support ticket because the option to set defaults is missing for me.

For anyone else trying to solve Azure mapping issues, these 2 pages help.

https://support.atlassian.com/jira-service-management-cloud/docs/import-information-from-microsoft-entra-id-into-assets/

https://support.atlassian.com/jira-service-management-cloud/docs/create-objects-from-data-using-object-type-mapping/

Marc -Devoteam- · Answer

Hi @Dave Furlani

The link you are providing relates to Jira DC (on-prem), thus doesn't apply to a Cloud instance.

In a scheme for each object you create an attribute is the key (just like in a db), this needs to be be set on creating an issue.

On the import you can specify what needs to be done if the key field is empty or multiple fields that need a value.

See https://support.atlassian.com/jira-service-management-cloud/docs/create-objects-from-data-using-object-type-mapping/

Or is this not what you meant?