Learn how Queues supports data residency to control where your app data is stored.
Data residency gives you control over where your in-scope app data is hosted. You can keep it in a specific geographic location to meet regulatory or internal governance requirements, or leave it set to Global so it moves dynamically across Atlassian’s regions.
For more information about data residency, see official Atlassian documentation.
Atlassian offers the following locations for data residency:
| Location | AWS regions |
|---|---|
| Global (default) | All Atlassian cloud regions |
| Australia | Sydney |
| Canada | Central |
| EU | Frankfurt, Dublin |
| Germany | Frankfurt |
| India | Mumbai |
| Japan | Tokyo |
| Singapore | Singapore |
| South Korea | Seoul |
| Switzerland | Zurich |
| United Kingdom | London |
| USA | US East (North Virginia), US West (Oregon) |
Queues is a Marketplace app, so its data can move together with your Jira site when you pin it to a new location. Depending on how the migration is triggered, some Marketplace apps move automatically during the Jira migration, while others move separately afterward.
During the move, your site may be offline for up to 24 hours depending on the amount of data, and search indexing can take up to three days to complete afterward.
For more information about moving apps data to another location, see official Atlassian documentation.
If you uninstall Queues, its region information is deleted. Reinstalling the app may result in a different location, which can affect where new data is stored.
If you can’t find the answer you need in our documentation, raise a support request. Include as much information as possible to help our support team resolve your issue faster.
Back to App page