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

Issue view and activity show inconsistent due dates, leading to user confusion

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low (View bug fix roadmap)
    • None
    • 7.4.6, 7.5.4, 7.3.9, 7.9.2, 7.7.4, 7.8.4, 7.10.2, 7.11.2, 7.13.1, 7.12.3, 7.6.11, 8.3.4
    • Issue - View Issue
    • None

      Problem

      Due dates may differ between the issue view and the activity stream when Jira timezone and user timezones are different.

      As an example, if the server is set with a GMT+0 timezone and an issue is set with a due date of 28 February, a user with a GMT-8 timezone will see the due date as 27 February in the general or user-specific activity streams.

      Because due date is a date field, rather than a date/time field, the due date will technically be 00:00:01 am on the 28th, which would be 16:00:01 pm GMT-8 on the 27th, hence the disparity.

       

      Steps to Reproduce

      1. Configure Jira with a GMT+0 timezone
      2. Add a user, set the user's timezone to GMT+0
      3. Add a second user, set the user's timezone to GMT-8
      4. Create a project and issue, assign a due date to that issue
      5. Login and view the issue as the first user, then the second user to see the due date disparity. The second user should see that the due date is the prior day, the first user should see the the due date as the expected day. In both cases the issue view will exhibit the expected due date.

      One Suggested Solution

      Change due date to be a date/time field and also display the timezone. This will help users to better understand why the dates are different and as a nice bonus allow to set a specific due time.

      Workaround

      None at this time.

            [JRASERVER-68781] Issue view and activity show inconsistent due dates, leading to user confusion

            Matt Doar added a comment -

            I think that Date fields have an implicit time of 00:00, so the start of the day. When the user's timezone of CMT-8 is applied then the date is the previous day. I agree that storing timezones with dates in the database would be the real solution, but that's a large change.

            Matt Doar added a comment - I think that Date fields have an implicit time of 00:00, so the start of the day. When the user's timezone of CMT-8 is applied then the date is the previous day. I agree that storing timezones with dates in the database would be the real solution, but that's a large change.

              Unassigned Unassigned
              troyall TJ Royall
              Affected customers:
              11 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated: