Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-12847

Filtering by date range on Date Attribute will show incorrect results if in Account preferences timezone is set to EMEA/APAC timezones

      Issue Summary

      Filtering by Date range on Date Attribute will show incorrect results if time zone in account preferences is set to any UTC+ (UTC+1, UTC+2...) timezone (EMEA/APAC regions).

      AMER and UTC timezones are working correctly.

      Steps to Reproduce

      1. Create Date attribute
      2. Create two objects and populate Date attribute with values 10-Jul and 11-Jul
      3. In Account preferences set timezone to timezone Europe/Berlin (UTC+2)
      4. Filter object list by Date range

      Expected Results

      • filter between 10-Jul and 10-Jul - will return object with date 10th Jul
      • filter between 11-Jul and 11-Jul - will return object with date 11th Jul, but not 10th Jul
      • filter between 11-Jul and 12-Jul - will return object with date 11th Jul.

      Actual Results

      • filter between 10-Jul and 10-Jul - no objects returned.
      • filter between 11-Jul and 11-Jul - returns object with date 10th Jul, but not 11th Jul.
      • filter between 11-Jul and 12-Jul - returns both objects with date 10th Jul and 11th Jul.

      Workaround

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

            [JSDCLOUD-12847] Filtering by date range on Date Attribute will show incorrect results if in Account preferences timezone is set to EMEA/APAC timezones

            There are no comments yet on this issue.

              7260236ab89d Justin King
              207d30156835 Ivan Chapistrak
              Affected customers:
              3 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated: