Uploaded image for project: 'Atlassian Cloud'
  1. Atlassian Cloud
  2. CLOUD-11839

Tempo Timesheets app data residency status changes back to eligible after a successful data residency migration.

    XMLWordPrintable

Details

    • 3
    • Severity 3 - Minor
    • Jira Software, Jira Service Management, Jira Work Management, Jira Product Discovery, Confluence

    Description

      Issue Summary

      When the data of the Tempo Timesheets app is pinned to a region using data residency, and the app gets an update, the data residency status changes back to eligible. This is just a UI bug and does not affect where the data is actually stored.

      Steps to Reproduce

      1. Pin the data of the Temp Timesheets app to the DE region using data residency.
      2. If the app has an update, the status changes back to eligible.

      Expected Results

      The status shows that the data is pinned to the DE region.

      Actual Results

      The status shows as eligible and the location shows as EU.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

      Attachments

        Activity

          People

            Unassigned Unassigned
            791737db6aab Venkatesh Chaturvedi
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: