...
Root object type name
Specify the name of the object type where the imported data will be stored. If the object type does not exist, it will be created automatically (*recommended).
Note : For existing object types, ensure they were created via import processes than through the GUI to avoid issues due to the Atlassian limitations (cross schema referencing).
Subscription ID
Note : Only resources registered under the specified subscription will be imported. To import asset data from multiple subscriptions, create separate importer instances with configurations for each subscription, or modify the existing one.
Application (Client) ID
Application (Client) Secret Key
...
You might encounter this error (2) when starting the import (1). The first thing to check is whether your license is active, as it is the most common reason. The quickest way to verify this is in the import configuration dialog (3), where a message should appear in such case.
...
Multiple subscription import
In the current version, one import instance can only import resources registered under the specified subscription.
To import asset data from multiple subscriptions, you need to create separate importer instances with distinct configurations for each subscription (or modify the existing one).
To make the import functional for another subscription, it is necessary to update not only the Subscription ID but also make sure to set correct Application (Client) ID with its Application Secret Key to grant access to subscription resources.
Feedback and Support
Your invaluable feedback fuels the evolution of Azure Jira Assets Sync. Share your insights, and together, we'll cultivate a more refined and impactful user experience! 📊🌱
...