Jira data residency leaves Marketplace apps with a separate move

Jira can move region. Its Marketplace apps get a vote.

Why it matters

The green residency badge belongs to Jira’s in-scope data. An installed Marketplace app can keep a separate timetable, a separate operator and, for a dedicated move, a full-day outage window. The region selector is the beginning of the purchase, not the receipt.

Mara Voss2 November 2026 at 14:24 UTCReading Time 2 minLast update: 2 November 2026

The host has moved; the connected app keeps another timetable. Conceptual illustration.

Summary

Atlassian pins in-scope data at the app level. Marketplace apps have their own residency status; only some can move with the host app.
A separate Marketplace migration needs at least three days’ notice and a 24-hour move window. Atlassian tells customers to plan for the host app to be offline during that window.

The badge and the baggage

A company moves Jira into a chosen region and sees PINNED in Atlassian Administration. That is a real control over in-scope Jira data. It is a poor inventory of everything attached to Jira. Marketplace apps are largely built by third parties, and Atlassian assigns them four different residency states. The procurement question is no longer “Where is Jira?” It is “Which installed app still has its own answer?”

PINNED means the Marketplace app is already aligned with its host. ELIGIBLE means the app supports pinning and movement into that location but has yet to arrive. NOT ELIGIBLE can mean the partner lacks residency support or the required location; some data inside Atlassian systems may nonetheless have moved. NO ACTION AVAILABLE is different again: the partner says the app stores data only in the host or stores none. Counting that last category as an offshore leak would be fiction.

The migration bill is paid in time as well as engineering. Some supported apps move immediately after the host during the scheduled maintenance. Others require a later request handled by the partner. For a separate move, Atlassian requires the request at least three days ahead, offers a 24-hour window, and says the host app will be offline while the partner moves data. The exact finish depends on that partner. A data-location checkbox has become a service-availability decision.

There is a sharper edge for an app that works with both Jira and Confluence. Atlassian says its data region follows the required host app, while all connected hosts can experience downtime during its move. An administrator who looks only at Jira’s badge may miss both the governing app and the affected service. The Marketplace Privacy and Security tab and the partner’s own policy are the documents to put beside the host status. Atlassian publishes no customer-specific count of apps in these states, so a universal exposure rate has no evidential home.