Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-12880

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

XMLWordPrintable

      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. screenshot1_updated.png
          screenshot1_updated.png
          35 kB
        2. screenshot1.JPG
          screenshot1.JPG
          26 kB
        3. screenshot2_updated.png
          screenshot2_updated.png
          34 kB
        4. screenshot2.JPG
          screenshot2.JPG
          20 kB

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

            Graeme Baker added a comment -

            please fix, its been fixed in cloud https://jira.atlassian.com/browse/JSWCLOUD-26565

            Graeme Baker added a comment - please fix, its been fixed in cloud https://jira.atlassian.com/browse/JSWCLOUD-26565

            Abby Domanowski added a comment -

            Our teams are encountering this issue, too, and one of the more frustrating parts is that it becomes hard to discern what the real date of the release is when different people see different dates (and even see different dates in different views). 

            For us, one of our users had profile settings set to "Dublin" and was seeing release date June 24 in the version configuration but release date June 23 on dashboards. For other users, they saw June 23 in both the version configuration and the dashboard.

            This is a localization problem and again, makes it difficult for teams to identify what date is accurate without checking everyone's personal time zone settings.

            Abby Domanowski added a comment - Our teams are encountering this issue, too, and one of the more frustrating parts is that it becomes hard to discern what the real date of the release is when different people see different dates (and even see different dates in different views).  For us, one of our users had profile settings set to "Dublin" and was seeing release date June 24 in the version configuration but release date June 23 on dashboards. For other users, they saw June 23 in both the version configuration and the dashboard. This is a localization problem and again, makes it difficult for teams to identify what date is accurate without checking everyone's personal time zone settings.

            Mithun Parvathaneni added a comment -

            This effects my team on version 9.12.8

            Mithun Parvathaneni added a comment - This effects my team on version 9.12.8

            anderson.todd added a comment -

            Will this ever be fixed?

            anderson.todd added a comment - Will this ever be fixed?

            Edward England added a comment -

            Does anyone know when this will be fixed?

            Edward England added a comment - Does anyone know when this will be fixed?

            Brent Nye added a comment -

            Please address this issue. Using Jira 8.13.2. Thank you.

            Brent Nye added a comment - Please address this issue. Using Jira 8.13.2. Thank you.

            Concentric Sky IT added a comment -

            Another vote to prioritize.  Our PM team considers this to lack adequacy.

            Concentric Sky IT added a comment - Another vote to prioritize.  Our PM team considers this to lack adequacy.

            Kyle added a comment -

            It's more than a minor annoyance, since every time you go to edit, even if you don't touch anything, the next time you save it the time will have jumped forward +8 hours (or wherever you are relative to GMT).

            Due to this bug, every time I edit my sprint description, the due date moves forward a day.  Try explaining that to your PM team.

            Kyle added a comment - It's more than a minor annoyance, since every time you go to edit, even if you don't touch anything, the next time you save it the time will have jumped forward +8 hours (or wherever you are relative to GMT). Due to this bug, every time I edit my sprint description, the due date moves forward a day.  Try explaining that to your PM team.

            hikeit added a comment -

            We're still running into this too.

             

            A basic timezone bug, that has been around for 5 years?? Impressive.

            hikeit added a comment - We're still running into this too.   A basic timezone bug, that has been around for 5 years ?? Impressive.

            Ryan Williams added a comment -

            This is something our enterprise development team has been dealing with for years now, and it still garners laughter every time we explain the bug to a new starter.

            Just another vote to please prioritise it if possible...

            Ryan Williams added a comment - This is something our enterprise development team has been dealing with for years now, and it still garners laughter every time we explain the bug to a new starter. Just another vote to please prioritise it if possible...

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

                Created:
                Updated: