Forge apps can store, retrieve, and delete data in Atlassian's cloud, either through Forge hosted storage or through each product.
Forge provides two classes of hosted storage options:
Persistent: to store data that you need to keep for long periods, until you need to delete or overwrite it. Forge's persistent storage options also provide data residency features that allow admins to control where app data is hosted (see Data residency for more information).
Cache (EAP): to store data that requires fast and frequent access, at the expense of persistence and encryption.
When a customer reinstalls an app that uses Forge hosted storage, data from the previous installation is not automatically restored. Forge hosted storage retains data for 14 days after uninstallation.
To recover this data for a customer, app developers must:
Get customer consent to restore data.
Submit a recovery request within 7 days of uninstallation. This is to ensure the request is processed before the 14-day retention ends.
To request recovery, raise a bug ticket on Developer Support. Use “Re-linking reinstallation data” as the summary, and provide customer details, site ID, and installation IDs.
Forge can also use product-specific APIs to store and retrieve data for Atlassian Cloud sites and workspaces. This data is accessible to all apps installed within the site (as well as users). See product REST APIs for more details.
Using the capabilities discussed in this section may make your app not eligible for Runs on Atlassian.
Go to this page to know more about the Runs on Atlassian program. To know how to check if your app is eligible for Runs on Atlassian, go to the Forge CLI documentation.
Forge also lets you integrate your app with services hosted on other platforms. This allows Forge apps to store data remotely on self-hosted databases or third-party storage services. For more information about integrating with remote services, see Forge remote.
Rate this page: