Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-41646

Releasing a version shows the Release Date one day behind the date originally set

XMLWordPrintable

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

      Summary

      If the user timezone and system timezones are different (and the system's timezone is one day ahead of the user's), JIRA will show the Release Date in the Release Version popup one day behind the release date in the Versions page.

      Environment

      • All JIRA versions (6.x, 7.x, 8.x)
      • System Timezone: Australia/Sydney
      • User Timezone: US/San Fransisco

      Steps to Reproduce

      1. Navigate to Administration » System » General Configuration and set the System Timezone to Australia | Sydney.
      2. Set your user's timezone to GMT-7.
      3. Add a version with a release date to a project.
      4. Select the ••• menu and 'Release' next to the version name.

      Expected Results

      The release date would be the same as defined in the version release date.

      Actual Results

      Original Description

      When setting up a version with Release Date of for example Dec 31, 2014. When trying to Release that date the pop-up model now shows one day prior in version v6.3.13. Prior versions did not change the release date to 1 day prior to that which has been set.

        1. 9.7.0_Issue.png
          9.7.0_Issue.png
          166 kB
        2. Jira VerDateBug-ManageVersions UI.JPG
          Jira VerDateBug-ManageVersions UI.JPG
          35 kB
        3. Jira VerDateBug-projectversionTable.JPG
          Jira VerDateBug-projectversionTable.JPG
          17 kB
        4. Jira VerDateBug-projectversionTable.JPG
          Jira VerDateBug-projectversionTable.JPG
          17 kB
        5. Jira VerDateBug-Versions UI.JPG
          Jira VerDateBug-Versions UI.JPG
          15 kB
        6. release-date.png
          release-date.png
          59 kB
        7. Screen Shot 2015-01-15 at 10.22.28 AM.png
          Screen Shot 2015-01-15 at 10.22.28 AM.png
          79 kB
        8. Screen Shot 2015-07-24 at 12.05.27 pm.png
          Screen Shot 2015-07-24 at 12.05.27 pm.png
          172 kB
        9. Screen Shot 2015-08-19 at 2.24.25 PM.png
          Screen Shot 2015-08-19 at 2.24.25 PM.png
          76 kB

            [JRASERVER-41646] Releasing a version shows the Release Date one day behind the date originally set

            Ludovic Allouch added a comment -

            Come on, Dark theme is much more important than that tiny bug...

            Ludovic Allouch added a comment - Come on, Dark theme is much more important than that tiny bug...

            Julie Barton added a comment -

            So this isn't really fixed if there is a new bug to track now???  Please explain how this makes sense.

            Julie Barton added a comment - So this isn't really fixed if there is a new bug to track now???  Please explain how this makes sense.

            Vic Mielczarek added a comment -

            Everybody, all the Watchers - it would be good if you voted for the new bug that is in Gathering Impact status

            • JRASERVER-76438 Release versions show the Release Date one day behind the date originally set

            Vic Mielczarek added a comment - Everybody, all the Watchers - it would be good if you voted for the new bug that is in Gathering Impact status JRASERVER-76438 Release versions show the Release Date one day behind the date originally set

            John Vecchio added a comment - - edited

            https://jira.atlassian.com/browse/JRASERVER-76438

            New bug to track this on going issue

            John Vecchio added a comment - - edited https://jira.atlassian.com/browse/JRASERVER-76438 New bug to track this on going issue

            Javier Andres Orellana Orellana added a comment -

            We have this issue in our Jira Data Center Instance (v8.20.10#820010)

            Javier Andres Orellana Orellana added a comment - We have this issue in our Jira Data Center Instance (v8.20.10#820010)

            rthompson added a comment -

            rthompson added a comment -

            rthompson added a comment -

            Still seeing this issue in Jira 8.20.10

             

            rthompson added a comment - Still seeing this issue in Jira 8.20.10  

            Kevin Liou added a comment -

            This issue appears to still be unresolved in Jira 9.7.0.

            System Time: Australia/Sydney (GMT+10)
            User Time: Chicago (GMT-6)

            Additionally, issue occurs even if System Time and User Time are the same (GMT-6)

            Kevin Liou added a comment - This issue appears to still be unresolved in Jira 9.7.0. System Time: Australia/Sydney (GMT+10) User Time: Chicago (GMT-6) Additionally, issue occurs even if System Time and User Time are the same (GMT-6)

            lhegde added a comment -

            Does this fix also fix the Cloud version issues? I see attached JRACLOUD-41646 issue is closed/fixed but date shows 2017.

             

            lhegde added a comment - Does this fix also fix the Cloud version issues? I see attached JRACLOUD-41646 issue is closed/fixed but date shows 2017.  

            alexander.dvorkin added a comment -

            To confirm, this fix is now available in version 9.7.0?

            alexander.dvorkin added a comment - To confirm, this fix is now available in version 9.7.0?

              afb6234f8e80 Mark Patterson (Inactive)
              5e5f0bfb640b Katherine B
              Affected customers:
              281 This affects my team
              Watchers:
              260 Start watching this issue

                Created:
                Updated:
                Resolved: