...
See which Object Types or Object Type Attributes have been added, removed, or updated.
Run the schema and mapping update to apply these changes.
Structuring Your Imports in Jira
...
Depending on your organization’s needs, you may want to import data from different subscriptions into one shared “root object” within Jira Assets or keep them separated by creating distinct root objects.
Single Root Object: All resources, regardless of the subscription, are imported into a single location within Jira Assets. This works well if it’s not necessary to distinguish resources by environment (e.g., production vs. testing), or to track resources across your organization and have everything in one place.
Separate Root Objects: If it’s essential to differentiate resources for example by environment, you can set up separate root objects within Jira for each subscription (multiple import instances). This setup reduces the risk of data confusion, as each environment is clearly separated in Jira Assets.
...
Note: If you had any IpConfigurations imported from a version prior to 3.15.0 and import them again, they will be treated as "duplicates" (since the Id attribute is being modified, the system sees it as a new object). To resolve this, we recommend bulk-removing all the existing IpConfigurations and then running the import again.
| Note |
|---|
|
As of February 4, 2025, imports in our app now have improved capacity. This enhancement allows for significantly higher subscription limits per session, making the import process more efficient. In most cases, this increased limit should be sufficient to meet all user needs.
While the exact limit may vary based on factors like the amount of data associated with each subscription, here’s what you need to know:
General Guidance on Limits:
In many cases, users may encounter restrictions around 350 subscriptions per session.
However, under certain conditions with smaller datasets per subscription, it is possible to import up to nearly 1000 subscriptions in a single session.
Real-World Variations:
Due to differences in data volume, some users may encounter import limitations at lower subscription counts. This variability makes it important to plan import sessions accordingly.
Workarounds for Larger Imports
If your organization has a high number of large subscriptions or encounters import limitations, consider these approaches:
Use Multiple Import Instances
Specify Individual Subscriptions
Consider running separate import sessions. This can be done by listing up to around 350 subscriptions per session in the Subscription IDs configurationinput field.Import “All Available” Subscriptions
Alternatively, you can create multiple Azure registration applications to divide and manage the subscription import process more effectively. Each app can be configured to import a different set of up to around 350 subscriptions, reducing manual input and simplifying the import setup (utilizing the "All Available" configuration option)
Troubleshooting
Assets - Azure Integration requires both Jira and Assets to function. Also make sure all the specific permission in your Azure environment was set right.
...
object HAVING inboundReferences()
...
Socket hang up error (ECONNRESET)
You might notice your import process appears to run endlessly without completing. This is due to an issue in the Forge platform, where the error occurs internally during calls to Atlassian’s API.
We have implemented a workaround that we believe resolves the issue; however, it may still occur as it is being tracked under ECO-516, and Atlassian is actively working on a permanent fix. If the issue does arise, the current solution is to manually stop the import and restart it. Please note that this issue can also occur during scheduled imports. As a result, we recommend monitoring scheduled imports and restarting them if necessary.
Feedback and Support
Your invaluable feedback fuels the evolution of Azure Sync for Jira Assets. Share your insights, and together, we'll cultivate a more refined and impactful user experience! 📊🌱
...