We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-26039

Verify the system timezone when an XML backup is restored

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      When migrating JIRA to another server, if there are timezone inconsistencies between the two servers it can cause considerable problems with the new server that may not be discovered until problems have been introduced into the dataset. Please enhance JIRA to timestamp an XML backup and provide a warning during XML restore that the backup does not match the server time of the instance it is being imported into.

      • Times stored in the database is based on the JIRA JVM user timezone

      Workaround

      In order to restore the times back to their last known working form, the below process can be used for the new server:

      1. Generate an XML backup from the previous server, or obtain the last-known working one and copy it to the new JIRA server.
      2. Schedule a downtime window.
      3. Stop the new JIRA server.
      4. Either:
        • Set the JVM timezone argument, e.g.: -Duser.timezone=GMT, as in Setting Timezone in JIRA.
        • Change the System Time of the server that the JVM is running on (the JVM will default to that time).
      5. Start the new JIRA server.
      6. Import the XML backup from the previous server.
      7. Test JIRA.

      If the server is unable to be rolled back, the below can be followed, however this is not the recommend method and may cause additional problems due to time inconsistencies.

      1. Schedule a downtime window.
      2. Export the XML backup.
      3. Stop JIRA.
      4. Either:
        • Set the JVM timezone argument, e.g.: -Duser.timezone=GMT, as in Setting Timezone in JIRA.
        • Change the System Time of the server that the JVM is running on (the JVM will default to that time).
      5. Start JIRA.
      6. Import the XML backup.
      7. Test JIRA.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-26039

            Verify the system timezone when an XML backup is restored

              • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

                NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

                When migrating JIRA to another server, if there are timezone inconsistencies between the two servers it can cause considerable problems with the new server that may not be discovered until problems have been introduced into the dataset. Please enhance JIRA to timestamp an XML backup and provide a warning during XML restore that the backup does not match the server time of the instance it is being imported into.

                • Times stored in the database is based on the JIRA JVM user timezone

                Workaround

                In order to restore the times back to their last known working form, the below process can be used for the new server:

                1. Generate an XML backup from the previous server, or obtain the last-known working one and copy it to the new JIRA server.
                2. Schedule a downtime window.
                3. Stop the new JIRA server.
                4. Either:
                  • Set the JVM timezone argument, e.g.: -Duser.timezone=GMT, as in Setting Timezone in JIRA.
                  • Change the System Time of the server that the JVM is running on (the JVM will default to that time).
                5. Start the new JIRA server.
                6. Import the XML backup from the previous server.
                7. Test JIRA.

                If the server is unable to be rolled back, the below can be followed, however this is not the recommend method and may cause additional problems due to time inconsistencies.

                1. Schedule a downtime window.
                2. Export the XML backup.
                3. Stop JIRA.
                4. Either:
                  • Set the JVM timezone argument, e.g.: -Duser.timezone=GMT, as in Setting Timezone in JIRA.
                  • Change the System Time of the server that the JVM is running on (the JVM will default to that time).
                5. Start JIRA.
                6. Import the XML backup.
                7. Test JIRA.

                        Unassigned Unassigned
                        73d805a2526b MattS
                        Votes:
                        3 Vote for this issue
                        Watchers:
                        11 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            73d805a2526b MattS
                            Votes:
                            3 Vote for this issue
                            Watchers:
                            11 Start watching this issue

                              Created:
                              Updated:
                              Resolved: