Can a mismatched data residency be solved by Atlassian support or by organization admin?

[Arthur Fraanje]

Requirements Yogi app for Jira was recently installed with existing Confluence and Requirements Yogi for Confluence.  Errors occurred when trying to associate the Confluence and Jira instances whilst ensuring both client keys match.

Support from Requirement Yogi identified our Jira is located in the US and Confluence in the EU and advised us to contact Atlassian Support to force a realm migration . Examination by our organization admin shows the data residencies are not set (Marketplace app status).

Does the admin need to set the data residencies (Set location), or does Atlassian support need to force a realm migration to fix the errors?

[Mohanraj Thangamuthu]

Hello, Good day. In this case Jira needs to be pinned to the required location and then connect addon can be pinned to the specific location as well. Admin will be able to perform both the activity . Please refer to the following link for steps https://support.atlassian.com/security-and-access-policies/docs/manage-data-residency-for-products/

[Arthur Fraanje]

Thankyou Mohanraj.

At present non of our apps are pinned as per attached pic. Can you please confirm our Jira is located in the US and Confluence in the EU and why are we not seeing this?

Should I just be only pinning Jira to match Confluence in the EU and thus leave other market place app status unchanged? (see attached pic)
When Jira is pinned for the first time, is it the same process as app data being pinned to a new location? I am concerned about downtime and loss of Jira links to Confluence.