Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-98215

Due date shows one day behind in confluence when timezone is set to PST timezone

XMLWordPrintable

    • 8.2
    • 1
    • Severity 2 - Major
    • 80
    • Hide
      Atlassian Update – 15 Oct 2024

      Dear Customers,

      We've performed an investigation into the cause of this bug, and it appears to be happening within Confluence itself. As a result I've moved this issue over to the Confluence DC backlog, assigned, and prioritised it. We're hoping to ship a resolution to this problem soon, thanks for your patience.

      Cheers,

      Michael Andreacchio
      Confluence DC Product Management

      Show
      Atlassian Update – 15 Oct 2024 Dear Customers, We've performed an investigation into the cause of this bug, and it appears to be happening within Confluence itself. As a result I've moved this issue over to the Confluence DC backlog, assigned, and prioritised it. We're hoping to ship a resolution to this problem soon, thanks for your patience. Cheers, Michael Andreacchio Confluence DC Product Management

      Issue Summary

      This is reproducible on Data Center: (yes)

      The due date shows one day behind in Confluence  as compared to Jira when the timezone is set to PST timezone in both Jira and confluence

      There is a similar problem with a different root cause with the Target start / Target end custom fields, which you can follow here: JSWSERVER-21994

      Steps to Reproduce

      1. Start Jira and add the Due date field to the create issue screen
      2. Make sure the system timezone is set to GMT +05:30 (Asia/Kolkatta) time zone for both Confluence and Jira
      3. Create a Confluence page and add the new issues created on the respective page including value for the Due date. Here you will see that the Due date shows just fine on the Confluence side 
      4. Now Change the OS time Zone to PST(i.e America/los angeles) 
      5. Install Jira and Confluence on this server 
      6. Repeat steps 1 and 3 and this time you will see that the Due date in Confluence shows one day behind 

      Expected Results

      The Due date should stay the same as it is reflected in Jira

      Actual Results

      The Due date shows one day behind in Confluence

      Workaround

      There is currently no workaround available.

        1. Screenshot 2022-03-07 at 10.48.53 PM.png
          Screenshot 2022-03-07 at 10.48.53 PM.png
          990 kB
        2. Screenshot 2022-03-07 at 10.45.35 PM.png
          Screenshot 2022-03-07 at 10.45.35 PM.png
          493 kB
        3. Screenshot 2022-03-07 at 10.48.57 PM.png
          Screenshot 2022-03-07 at 10.48.57 PM.png
          472 kB
        4. Screenshot 2022-03-07 at 10.45.03 PM.png
          Screenshot 2022-03-07 at 10.45.03 PM.png
          510 kB
        5. Screenshot 2022-03-07 at 10.44.41 PM.png
          Screenshot 2022-03-07 at 10.44.41 PM.png
          300 kB

            [CONFSERVER-98215] Due date shows one day behind in confluence when timezone is set to PST timezone

            Ethan Malasky added a comment - - edited

            Was this fixed for Target Start and Target End as well as for Due Date?  Or are those not really Duplicates, and need to be fixed with Jira updates? 

            Running Confluence 8.5.18 and Jira Data Center 9.12.12, still seeing Target End one day earlier in Confluence compared to Jira

            Ethan Malasky added a comment - - edited Was this fixed for Target Start and Target End as well as for Due Date?  Or are those not really Duplicates, and need to be fixed with Jira updates?  Running Confluence 8.5.18 and Jira Data Center 9.12.12, still seeing Target End one day earlier in Confluence compared to Jira

            Quan Pham added a comment -

            A fix for this issue is available in Confluence Server and Data Center 9.2.0. Upgrade now or check out the Release Notes to see what other issues are resolved.

            Quan Pham added a comment - A fix for this issue is available in Confluence Server and Data Center 9.2.0. Upgrade now or check out the Release Notes to see what other issues are resolved.

            Quan Pham added a comment -

            A fix for this issue is available in Confluence Server and Data Center 8.5.18. Upgrade now or check out the Release Notes to see what other issues are resolved.

            Quan Pham added a comment - A fix for this issue is available in Confluence Server and Data Center 8.5.18. Upgrade now or check out the Release Notes to see what other issues are resolved.
            Quan Pham made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            SET Analytics Bot made changes -
            UIS Original: 63 New: 80
            SET Analytics Bot made changes -
            Support reference count Original: 50 New: 1
            SET Analytics Bot made changes -
            UIS Original: 62 New: 63

            Pankaj Rana added a comment - - edited

            Any tentative timeline and in which LTS of Confluence data center the fix will be released? The latest LTS is 8.5.17 and this fix is not included in this version.

            Pankaj Rana added a comment - - edited Any tentative timeline and in which LTS of Confluence data center the fix will be released? The latest LTS is 8.5.17 and this fix is not included in this version.
            Arpan Agrawal made changes -
            Fix Version/s New: 7.19.30 [ 110397 ]
            Status Original: Awaiting Merge [ 10064 ] New: Waiting for Release [ 12075 ]
            SET Analytics Bot made changes -
            UIS Original: 61 New: 62

              3061d200deff Arpan Agrawal
              skaur@atlassian.com Saranjeet Kaur (Inactive)
              Affected customers:
              49 This affects my team
              Watchers:
              63 Start watching this issue

                Created:
                Updated:
                Resolved: