You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Atlassian Marketplace and our community of app developers play a critical role in helping our customers get the most value out of Jira Service Management's Assets. As we continue to work through enabling third party integrations for Assets in Cloud, we have just completed a major milestone by onboarding Assets to Forge and making our import APIs available via the platform. This means that:
Apps built on Atlassian’s Forge platform can now integrate directly with the Assets UI
Forge app developers can now integrate straight into the Assets UI by creating and registering their own custom import types. Find out more in our Forge integration guide for Assets
Forge apps for Assets will now comply with the Atlassian security requirements
Forge apps for Assets will no longer need exceptions to the security requirements for cloud apps, which dictate that “an application must not collect or store credentials belonging to Atlassian user accounts such as user passwords or user API tokens”. As authentication can happen via Oauth2.0, this also means that configuration of apps is now much simpler, since user or container tokens are no longer required to make integrations work.
Calls to Assets external imports no longer count toward Forge limits
Forge apps have strict call limits imposed. Since Assets in Jira Service Management is now onboarded as an internal Atlassian service, calls to Assets are not counted towards that limit.
App developers can get started quickly by using our customised template
We have also rolled out a template to help you get started with integrating. The template includes a manifest with all of the components needed to get started with your Assets-Forge integration. Simply update the manifest with your appId and start your built process!
Tips on how app developers can overcome Forge's invocation limits and create import apps at scale
With Forge's default 25-second invocation limit, apps previously were only able to offer limited scalability. We have created a guide on how to structure import jobs to bypass those limitations in order to create highly scalable import apps using Forge.
Please note: Assets in Jira Service Management (a.k.a. ‘Assets’) is separate from the “External Assets platform” which predates our native CMDB capability. For a full integration with Jira Service Management’s CMDB capability, we recommend integrating with Assets directly. For more information about Assets in Jira Service Management visit https://www.atlassian.com/software/jira/service-management/features/itsm#asset-management