Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-8710

Date values inconsistency for timezone GMT-XXX

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • Mindville - Pre Bundled, 4.19.0, 5.4.5
    • Assets - Core experiences

      Issue Summary

      Dates lagging one day are saved in the Database when using Type Value Date attribute in Insight and Server timezone is GMT-XXX.

      Steps to Reproduce

      • Set up a Jira instance with Insight 8.9.1 with America/Los_Angeles TimeZone (GMT-8)
      • Ensure Server - Jira Timezones are all set to:
        • jira.default.timezone: America/Los_Angeles
        • jvm.system.timezone : US/Pacific
        • Mysql Database Timezone: PDT

      • Create an Object Type and add a Date Attribute

         
      • Create an object and set a date, for instance, 12/Sep

      Expected Results

      Date should be stored as 2021-09-12

      Actual Results

      Date is stored as 2021-09-11 17:00:00.
      Exactly -7 hours (Pacific Daylight Time) behind GTM

      Query to get an attribute value:

      SELECT 
       OTA.NAME OTA_NAME,
      	OAV.DATE_VALUE 
FROM AO_8542F1_IFJ_OBJ O
         LEFT OUTER JOIN AO_8542F1_IFJ_OBJ_ATTR OA ON O.ID = OA.OBJECT_ID
         LEFT OUTER JOIN AO_8542F1_IFJ_OBJ_TYPE_ATTR OTA ON OTA.ID = OA.OBJECT_TYPE_ATTRIBUTE_ID
         LEFT OUTER JOIN AO_8542F1_IFJ_OBJ_ATTR_VAL OAV ON OA.ID = OAV.OBJECT_ATTRIBUTE_ID
WHERE OA.OBJECT_ID = 4 and OTA.NAME = 'Date'

      The below call is made in the atlassian-jira.log.log file. We observed date is already incorrect.

      2021-09-13 07:00:59,301-0700 http-nio-8080-exec-2 admin 420x1374x1 14mz3i7 /rest/insight/1.0/object/create 3 ms "INSERT INTO AO_8542F1_IFJ_OBJ_ATTR_VAL (OBJECT_ATTRIBUTE_ID,ADDITIONAL_VALUE,INTEGER_VALUE,DOUBLE_VALUE,TEXT_VALUE,DATE_VALUE,REFERENCED_OBJECT_ID,BOOLEAN_VALUE) VALUES (?,?,?,?,?,?,?,?)" {1=23, 2=null, 3=null, 4=null, 5=null, 6=2021-09-11 17:00:00.0, 7=null, 8=null}

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

        1. image-2021-09-16-10-44-26-487.png
          image-2021-09-16-10-44-26-487.png
          209 kB
        2. image-2021-09-16-10-55-40-203.png
          image-2021-09-16-10-55-40-203.png
          59 kB
        3. image-2021-09-16-11-03-03-920.png
          image-2021-09-16-11-03-03-920.png
          15 kB
        4. image-2021-09-16-11-03-45-333.png
          image-2021-09-16-11-03-45-333.png
          56 kB
        5. image-2021-09-16-11-06-51-724.png
          image-2021-09-16-11-06-51-724.png
          149 kB

            [JSDSERVER-8710] Date values inconsistency for timezone GMT-XXX

            Bartosz Ornatowski made changes -
            Status Original: Short Term Backlog [ 12074 ] New: Gathering Impact [ 12072 ]
            Bartosz Ornatowski made changes -
            Labels Original: ril New: nnb-dec ril
            Marc Dacanay made changes -
            Labels New: ril
            Marc Dacanay made changes -
            Remote Link New: This issue links to "Internal ticket (Web Link)" [ 955313 ]
            Marc Dacanay made changes -
            Labels Original: lts10nth
            Bartosz Ornatowski made changes -
            Sprint New: LTS Sprint [ 7234 ]
            Bartosz Ornatowski made changes -
            Status Original: Gathering Impact [ 12072 ] New: Short Term Backlog [ 12074 ]
            Bartosz Ornatowski made changes -
            Labels New: lts10nth
            SET Analytics Bot made changes -
            UIS Original: 2 New: 0
            SET Analytics Bot made changes -
            Support reference count Original: 2 New: 3

              Unassigned Unassigned
              9f03f4114502 Pablo Bartolome
              Affected customers:
              3 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated: