Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-15260

Update Upgrade Documentation to WARN on Timezone

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Done
    • Documentation
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      There is a crucial information missing in Migrating JIRA applications to another server around different server timezone. Having different time zone between the source server and target server can break Agile reports due to https://jira.atlassian.com/browse/JSW-5433

      Suggested Solution

      Include a colored warning in the particular document and related document stating something similar to

      Migrating to another server that has different timezone can break JIRA Software reporting. See https://jira.atlassian.com/browse/JSW-5433

      Why this is important

      It breaks JIRA Software reporting that is being used by Agile users. Representation of issues that are closed in a Sprint can vary.

      Workaround

      To re-run the XML restore that can take hours to complete, the full steps are explained in https://jira.atlassian.com/browse/JSW-5433

            [JSWCLOUD-15260] Update Upgrade Documentation to WARN on Timezone

            Wazza added a comment -

            Docs updated to make it clear source and target instances need to be on the same timezone to avoid any date and/or time field incompatibility. 

            Wazza added a comment - Docs updated to make it clear source and target instances need to be on the same timezone to avoid any date and/or time field incompatibility. 

              aicamen iceman
              znoorsazali Zul NS [Atlassian]
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: