Skip to content
English - United Kingdom
Sign in
  • There are no suggestions because the search field is empty.

How Date Filters and Fields Work Across Time Zones

Date range filters

  • Display exactly as you select:

    When a user selects a date filter, for example, 1st January 2025 to 31st December 2025, the filter will display those exact dates. What you pick is what you see in the filter, no matter your time zone.

  • How dates are calculated: 

    While the filter shows the dates you select, the after-filtering result is calculated in UTC (Coordinated Universal Time). For example, a range from 1st January 2025 to 31st December 2025 includes items from 00:00 UTC on 1st January through 23:59 UTC on 31st December. This ensures that users in different time zones see the same results, and that timestamps are displayed in each user’s local time zone.

    Example: why a case may appear as the previous local day

    Suppose two cases were created at:

    • 02:00 UTC on 1st January 2025
    • 02:00 UTC on 1st January 2026

    A user in San Francisco (UTC−07:00) sees these as 17:00 on the previous local day:

    • 31st December 2024
    • 31st December 2025

    If the user filters from 1st January 2025 to 31st December 2025:

    • The first case (02:00 UTC on 1st January 2025) is included.
    • The second case (02:00 UTC on 1st January 2026) is correctly excluded.

Date fields

  • Fields that capture only a date (without a time) are not affected by time zones. The date you enter is the date that is stored and displayed for all users, regardless of their location.
    For example: If a user in San Francisco enters 15 March 2025 in a date field, a user in a CET time zone will also see 15 March 2025, and vice versa.

Date/Time fields 

  • When you enter a date and time, it is captured in your local time zone, converted to UTC for storage, and then displayed back to each user in their own local time zone.

    For example: A user in San Francisco enters 15 March 2025 at 17:00 local time. It’s stored as 02:00 UTC on 16 March 2025. A user in a CET time zone sees the same field as 03:00 local on 16 March 2025 (assuming a +01:00 offset).

  • Seeing items a day earlier or later than expected? Check if you’re looking at local display times for records that were included using UTC boundaries.
  • Comparing results with a colleague in another time zone? Make sure you both applied the same calendar dates. The results should match because inclusion is UTC-based.
  • The stored source of truth for date-time fields is UTC, while the times you see on screen are shown in your local time for readability.
  • To understand different Date fields, check out Understanding Date Fields.