Connect apps for Confluence Cloud and Jira Cloud can now incrementally adopt powerful Forge capabilities, all while keeping their existing features, installations and reviews.
In minutes, you get access to:
New product integration points, such as
Immediate app updates to your customers (for non-admin-approved updates)
Forge storage (allowing more complex data structures and filtering than Entity Properties)
Forge functions and Forge UI (run for you by Atlassian)
Access to Oauth 2.0 REST APIs (not available to Connect)
GraphQL APIs from your backend
These are available without needing to change anything about your existing Connect code.
No. You can add Forge features while keeping some or all of your Connect modules.
The Forge parts of your app can communicate with your existing Connect server using Forge remote, which is seamlessly supported by official Connect frameworks.
Your app will keep its existing listing with its reviews and installations. When you add the Forge version to your existing marketplace listing, your customers will be notified of a new version and invited to upgrade via the "Manage apps" screen, as usual. See Listing your Forge successor app on Marketplace for more details.
Yes. Adopting, extending and testing your app with Forge is a safe process and will not affect your current Connect app or customers.
Existing and new installations of your app will only see the Forge version when it is added and approved as a new version to your marketplace listing.
Right now, some incompatibilities may stop your app from adopting Forge.
No.
The whole process can be done in under an hour.
Once you've checked the limitations and differences, let's adopt Forge from Connect.
Rate this page: