Per-App Data Residency Migration Status in Admin Hub

XMLWordPrintable

    • 1
    • Jira Software, Jira Service Management, Confluence

      Summary

      Display individual migration and pinned status per app in Admin Hub (admin.atlassian.com), rather than rolling all apps into a single site-level status that shows "Not Set" or "Move Delayed" while sequential migrations are in progress.

      Problem

      • Sequential Pacing: Forge apps migrate one at a time per maintenance window. For customers with weekly or 5-day notice policies, migrations can span weeks.
      • Misleading UI: If App A finishes and pins to the target realm while App B awaits the next window, Admin Hub marks all apps as "Not Set" or "Move Delayed".
      • Requires Atlassian Support: Admins assume the migration is encountering issues, generating support requests to verify backend completion.

      Proposed Solution

      1. Per-App Status Table: Show individual statuses (Pinned, In Progress, Scheduled for <Date>, Failed) for each app.

      2. Immediate Pinned Updates: Mark each app as Pinned as soon as its individual move completes, rather than waiting for the entire cohort.

      3. Progress Indicator: Display an overall tracker (e.g., “1 of 2 apps pinned — next app scheduled for Sep 19, 2026”).

      4. Accurate Delay Flags: Reserve "Move Delayed" for actual failures or timeouts, not expected intervals between maintenance windows.

              Assignee:
              Unassigned
              Reporter:
              Christopher Coykendall
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated: