This page describes how to request to persist the Connect app account in a new Forge app.
It also covers the situations when persisting the app account is required, as well as any considerations and constraints.
If one or more of your customers have interacted with your Connect app's account in a manner which needs to be preserved when moving to Forge, requesting app account persistence will enable you to do that. Some examples where you may need to preserve the account include:
If your customers need to add or modify the permissions for your Connect app's account in Confluence on the page level.
If your customers need to add or modify the permissions for your Connect app's account in Jira Global or Project Permissions.
Modify existing comments or content created by the app retrospectively including content stored by your app that is not visible to users, where modification of that content is only possible by the app.
You should not need to persist your Connect app's account to perform any other existing behaviours as an App, as your app will still be able to do this while on Forge. Apps will continue to have access to any entity properties once they have migrated to Forge without needing to persist their app account.
An app account can only be persisted for the Forge production environment. A new app account will be created for development and staging environments. Those new app accounts will not have access to the persisted app account's permissions or data.
Your request to persist your app account must be completed before the first time you deploy to production. If you have already deployed your app to production, you will need to register a new Forge app with a new app ID.
A Connect app account can only be associated with one Forge app.
Only Marketplace Connect app accounts can be persisted to Forge.
Persisting app accounts requires a manual process by our team members. You can create a Developer and Marketplace support ticket requesting to persist your app account with the following information:
Connect app key of the Connect app account;
Forge App ID of the Connect on Forge app;
Our support team will persist the app account and get back to you once the process is done (estimated response time is 4 hours). Then you can deploy your Connect on Forge app to the Forge production environment.
Rate this page: