Data Residency - Connect

Jira Development Jira Cloud
, ,
1

Hello,

We all know Connect won’t last for a long time.

But migrating data between regions using the Data Residency feature takes a lot of time to schedule the migration - ~3 days. This turns development and releases that impacts the data residency feature REALLY slow.
In the past, there was a way to manually trigger a migration by opening a support ticket somewhere. How can we do it know? I don’t want to call a single endpoint used for the migration, but simply start a migration that uses the all data residency flow.

Best,
Paulo Alves.

8 Likes
2

Hello,
This is probably also an issue on forge applications using remotes. A way to speed up the testing of the data residency workflow will be much appreciated.
Can we imagine an end-point on Atlassian side that trigger’s a dry-run migration ?

2 Likes
3

With the most recent change from Atlassian, only paid-enterprise instance (no enterprise trials) can trigger data migrations, it’s even more complicated now to support data residency for apps.

2 Likes
4

An answer from Atlassian would be much appreciated :neutral_face:

1 Like