The date/time asset attribute wrongly adds an extra hour for values during Daylight Saving Time (DST).

XMLWordPrintable

    • 1
    • Severity 3 - Minor

      Issue Summary

      Configure the default user time zone to a region that observes Daylight Saving Time (DST). In the example below, the time zone is set to (GMT+01:00) Warsaw, where DST is implemented from the last Sunday in March at 02:00 CET until the last Sunday in October at 03:00 CEST. Consequently, if an asset attribute of type date/time is configured, any date specified during the DST period will be displayed with an additional one-hour offset. For example, if an object is created with an attribute value of 05/May/25 12:34 PM or 25/May/26 10.00 PM, the asset will display the corresponding dates as 05/May/25 1:34 PM and 25/May/26 11.00 PM, respectively.

      Steps to Reproduce

      • Set the time zone to (GMT+01:00) Warsaw
      • Create an attribute of type Datetime
      • Create an object with an attribute value set to any date during the DST period, e.g. 10 May 2026, 10 PM.

      Expected Results

      Attribute values should be displayed exactly as entered. For example, in Jira issues, a date-time custom field present the value without any one-hour offset.

      Actual Results

      If an object is created with an attribute value of 05/May/25 12:34 PM or 25/May/26 10.00 PM, the asset will display the corresponding dates as 05/May/25 1:34 PM and 25/May/26 11.00 PM, respectively.

      Workaround

      Required, if there is no workaround please state:
      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Nick Austen
              Reporter:
              Navneeth S
              Votes:
              6 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: