In November 2022, we announced the early access program for Connect app realm migration. During this period, partners have had access to the APIs and underlying service in order to start building these capabilities into their apps. We are now approaching the release of the corresponding customer UI in the admin panel, which will begin a slow rollout on March 29, 2023.
On March 29 2023, the ability to use realm pinning and realm migration functionality will surface in admin.atlassian.com and we anticipate ~1,000 customers will see their existing apps’ data residency options. This functionality will be tagged with a ‘beta’ label. There will be no formal announcement drawing attention to this functionality throughout the duration of the Early Access Program.
Realm Migration for Connect apps will remain in the Early Access Program stage as it is today, and we plan to officially transition into the Preview release stage once we have tested the demand and functionality with early adopter partners and customers. Although Realm Migration will still be considered in EAP, partners who have successfully tested Realm Migration and have confirmed it is functioning as expected have the option to make it available to customers. This way, customers will have the chance to test this out as part of their Beta as well.
We are targeting June 2023 for the partner Preview* release and full rollout of the Customer UI Beta.
|Anticipated customer views per month||Target date/month|
|March 29, 2023
April 30, 2023
June 30, 2023
*Preview means that the feature is available for production use, and that a 1-3 month deprecation period and notice is provided for any breaking changes that may be introduced.
The customer facing UI will show details regarding realm pinning and realm migration. If an installed app supports realm migration, it will show which realms are available for pinning as well the current pinning status, including whether the app is compliant based on the host product pin location. If the app does not support realm migration, then it will show a status saying ‘Not Eligible’.
With this first release, we anticipate ~1,000 customers with self-service data residency enabled for JSW, JSM, or Confluence Cloud will see their existing apps’ data residency options on admin.atlassian.com.
These options include:
- Pinned: Apps have data pinned to a realm.
- Eligible: Apps are eligible to move to the same realm as the parent product.
If the customer’s parent product (Jira/Confluence) has data pinned to a region, customers will also see a new option to “Move apps” to the parent product region from within the data residency tab.
Clicking “Move apps” will allow customers to set a window of time to migrate all “eligible” apps that:
- support data residency in the region of the host product and
- support automated realm migration
For example, if a customer has their Jira Cloud data pinned to the United States, they can click “Move apps” to migrate data for apps that offer data residency in the United States.
Click into the product to see attached apps
Customers can tab between eligible apps, pinned apps, and ‘not eligible apps’ or apps that do not support (or do not need) data residency
Customers can schedule a window of time to migrate app data for apps that support realm migration
All apps that can move will do so during a pre-set window of the customer’s choosing. Apps will only be able to migrate data while the host product is offline, so customers should plan for some downtime during this process.
Feedback & questions
As we begin to see customers leverage your Connect app’s current realm pinning/migration capabilities, we’ll be monitoring both partner and customer feedback closely. Please leave any questions or feedback on this post directly, or send a direct message to me here on the developer community.
Why are we starting to release this now?
- Realm pinning has been available for some time now and even though partners have made substantial investment in it, customers don’t currently have a way to see which of their apps are pinned. With the new UI, partners who have invested in realm pinning can begin to highlight this work to customers. We believe that starting to observe customer adoption through a slow rollout is the best next step to help allow partners to reap the benefits of their investments.
What if I store data in Jira and Confluence?
- If you store data exclusively within Jira and Confluence, the data will inherit data residency controls already available for these products, therefore you do not need to support Connect Data Residency realm pinning and migrations.
When can I indicate support for a realm?
- If you indicate support for a realm, it means your app stores the relevant, in-scope data only in that realm - any in-scope data that your app stores must be stored in that realm. You should not declare the regionBaseURL for any realm unless you use storage infrastructure in that region to store in-scope customer data.
What if I don’t store any customer data?
- It is recommended to support data residency if your app stores end user data. Atlassian has outlined what is considered in-scope for data residency for its products here. If your app does not store any data, then your responses to your Privacy and Security should reflect what data your app uses/stores to help inform customers.
What should customers do if they see that an app is ‘not eligible’ to move and are not able to use the Realm Migration functionality?
How will customers know this is an EAP?
- There will be a ‘Beta’ label for Connect app data residency in the customer UI, indicating that this functionality is not yet fully in production.
Is there an update on Forge data residency?
- Please read this community post for the most recent update on Forge data residency.