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

Version's date is shown one day off on agile board>versions

      JIRA v6.3.8, JIRA Agile v6.6.13
      1. Go to project Overview>Versions (or project Administration>Versions) and observe a release date for certain version (in my example on the screenshot1.jpg it will be 22/Jan/15)
      2. Go to appropriate Agile board where this release will be represented, expand versions from the left, and observe the date of the same release

      Release date will be shown one day back (in my example on the second screenshot2.jpg it will be Release Date: 21/Jan/15)

      Steps to Reproduce

      We simply need to make JIRA's "Default user time zone" mismatch with Java's recognized "System Default". Let's assume the current Java "System Default" is: America/Los_Angeles (GMT -7)

      Reproduce 1
      1. Create a new Agile board, using the Sample Scrum Project
        • This will automatically include versions with release dates
      2. Within JIRA, modify JIRA Administration > System > General Configuration > Default user time zone
      3. Change the region to "Australia" and "GMT +8"
      4. Now compare the version dates on the Agile Board vs. the Project administration page - notice that they are a day off
      Reproduce 2
      1. Modify the JVM parameters to include: -Duser.timezone=Australia/Perth
      2. Restart JIRA and compare versions

      Workaround

      Ensure that both "Default user time zone" and JVM timezone match

        1. screenshot2.JPG
          screenshot2.JPG
          20 kB
        2. screenshot1.JPG
          screenshot1.JPG
          26 kB
        3. screenshot1_updated.png
          screenshot1_updated.png
          35 kB
        4. screenshot2_updated.png
          screenshot2_updated.png
          34 kB

            [JSWCLOUD-12880] Version's date is shown one day off on agile board>versions

            We have the same issue on

            • v7.3.2#73013

            http://www.screencast.com/t/jSeUAMmX

             

            Trevan Householder_Isos-Tech-Consulting_ added a comment - We have the same issue on v7.3.2#73013 http://www.screencast.com/t/jSeUAMmX  

            Sorry, the video... [^jira-release-date.mp4]

            (use this link if it didn't upload well)

            https://dl.dropboxusercontent.com/u/9297234/jira-release-date.mp4

            Deleted Account (Inactive) added a comment - Sorry, the video...  [^jira-release-date.mp4] (use this link if it didn't upload well) https://dl.dropboxusercontent.com/u/9297234/jira-release-date.mp4

            I have a similar issue when releasing. The release date is always wrong. Please, check the screencast. 

            [^jira-release-date.mp4]

            Deleted Account (Inactive) added a comment - I have a similar issue when releasing. The release date is always wrong. Please, check the screencast.  [^jira-release-date.mp4]

            I am seeing the problem when I look at release dates in the Releases screen - the dates are 1 day earlier than they should be. When I click Manage Versions, then the table updates so that all the dates are what they should be: they all are 1 day later. The system default timezone is the same as my personal default timezone.

            David Pirkle added a comment - I am seeing the problem when I look at release dates in the Releases screen - the dates are 1 day earlier than they should be. When I click Manage Versions, then the table updates so that all the dates are what they should be: they all are 1 day later. The system default timezone is the same as my personal default timezone.

            April added a comment -

            I have this exact problem in Jira 7.1.7. If I try to release a version, I get myDate - 1 as the release date.

            Default user time zone is set to System default: (GMT-05:00) New York, and my preferences are set to (GMT-06:00) Chicago.

            Even if I also set my user preferences to match System, I can still reproduce this error.

            Therefore, I do not think time zone mismatch is currently at fault.

            April added a comment - I have this exact problem in Jira 7.1.7. If I try to release a version, I get myDate - 1 as the release date. Default user time zone is set to System default: (GMT-05:00) New York, and my preferences are set to (GMT-06:00) Chicago. Even if I also set my user preferences to match System, I can still reproduce this error. Therefore, I do not think time zone mismatch is currently at fault.

            David Chan added a comment - - edited

            Reproduced on:

            • JIRA 6.4.12
            • Agile 6.7.11

            Problem looks to be due to a mismatch of of "Default user time zone" and "System Default"

            • Agile Boards are using the "Default user time zone", which is set within JIRA's administration screen
              • JIRA Administration > System > General Configuration > Default user time zone
            • Other parts of JIRA make use of the "System Default", which is the timezone that the Java environment recognizes
            • The problem occurs when the "System Default" is different than what's been set within the "Default user time zone"

            Steps to Reproduce

            We simply need to make JIRA's "Default user time zone" mismatch with Java's recognized "System Default". Let's assume the current Java "System Default" is: America/Los_Angeles (GMT -7)

            Reproduce 1
            1. Create a new Agile board, using the Sample Scrum Project
              • This will automatically include versions with release dates
            2. Within JIRA, modify JIRA Administration > System > General Configuration > Default user time zone
            3. Change the region to "Australia" and "GMT +8"
            4. Now compare the version dates on the Agile Board vs. the Project administration page - notice that they are a day off
            Reproduce 2
            1. Modify the JVM parameters to include: -Duser.timezone=Australia/Perth
            2. Restart JIRA and compare versions

            David Chan added a comment - - edited Reproduced on: JIRA 6.4.12 Agile 6.7.11 Problem looks to be due to a mismatch of of "Default user time zone" and "System Default" Agile Boards are using the "Default user time zone", which is set within JIRA's administration screen JIRA Administration > System > General Configuration > Default user time zone Other parts of JIRA make use of the "System Default", which is the timezone that the Java environment recognizes The problem occurs when the "System Default" is different than what's been set within the "Default user time zone" Steps to Reproduce We simply need to make JIRA's "Default user time zone" mismatch with Java's recognized "System Default". Let's assume the current Java "System Default" is: America/Los_Angeles (GMT -7) Reproduce 1 Create a new Agile board, using the Sample Scrum Project This will automatically include versions with release dates Within JIRA, modify JIRA Administration > System > General Configuration > Default user time zone Change the region to "Australia" and "GMT +8" Now compare the version dates on the Agile Board vs. the Project administration page - notice that they are a day off Reproduce 2 Modify the JVM parameters to include: -Duser.timezone=Australia/Perth Restart JIRA and compare versions

            Thank you!

            Nataliya Guner added a comment - Thank you!

            Klaus added a comment -

            You're right, nguner.
            Sorry for missing this important information present on your description.

            I will reopen this issue and keep it linked with the first one, as they probably could be fixed at the same time by the future developer.

            Cheers,
            Klaus.

            Klaus added a comment - You're right, nguner . Sorry for missing this important information present on your description. I will reopen this issue and keep it linked with the first one, as they probably could be fixed at the same time by the future developer. Cheers, Klaus.

            Nataliya Guner added a comment - - edited

            Hello Klaus,

            Thank you for follow up.
            I believe there are 2 different problems. We have seen the bug that is described in https://jira.atlassian.com/browse/JRA-41280 earlier, therefore I specifically mentioned that versions dates are the same in Administration>Versions and Overview>Versions. This bug (JIRA-41280) was fixed in our upgraded version JIRA v6.3.8 + JIRA Agile v6.6.13. Please refer to my screenshot1_updated.jpg in the bug – you will see the snapshots with the similar correct dates for both Administration>Versions and Overview>Versions.

            Bug that I’m pointing in the issue JIRA-41422 is for incorrect date (one day off) on Agile board>Versions (refer to screenshot2_updated.jpg)
            Please advise.

            Thank you,

            Nataliya

            Nataliya Guner added a comment - - edited Hello Klaus, Thank you for follow up. I believe there are 2 different problems. We have seen the bug that is described in https://jira.atlassian.com/browse/JRA-41280 earlier, therefore I specifically mentioned that versions dates are the same in Administration>Versions and Overview>Versions. This bug (JIRA-41280) was fixed in our upgraded version JIRA v6.3.8 + JIRA Agile v6.6.13. Please refer to my screenshot1_updated.jpg in the bug – you will see the snapshots with the similar correct dates for both Administration>Versions and Overview>Versions. Bug that I’m pointing in the issue JIRA-41422 is for incorrect date (one day off) on Agile board>Versions (refer to screenshot2_updated.jpg) Please advise. Thank you, Nataliya

            Klaus added a comment - - edited

            Hi nguner,
            thanks for submitting this issue to us.

            I've linked this issue with a previously reported one, as they both describe the same problem.
            Please, also consider watching the linked issue to receive immediate notifications as soon as they are available.

            Klaus added a comment - - edited Hi nguner , thanks for submitting this issue to us. I've linked this issue with a previously reported one, as they both describe the same problem. Please, also consider watching the linked issue to receive immediate notifications as soon as they are available.

              Unassigned Unassigned
              9f6488e17651 Nataliya Guner
              Affected customers:
              16 This affects my team
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: