Time zones and daylight saving

Each schedule has its own IANA time zone (for example Europe/Paris). It defaults to the zone in your Preferences, else the administrator’s default, else your own time zone.

Choosing a time zone

In the time zone picker, type a city or the name you use:

Times are shown with the zone’s name and city, for example 09:00 EDT (New York), or the offset for a fixed zone (09:00 UTC-05:00). The name is shown only when it matches the zone’s real offset at that moment; otherwise you see the city and its GMT offset, as for Vancouver (GMT-7) (British Columbia keeps UTC-7 all year from November 2026).

Clock changes

| Situation | What RepeatWise does | Example (Paris) | |—|—|—| | The time does not exist (spring forward) | Uses the first valid minute after the gap | 02:30 on 2027-03-28 becomes 03:00 | | The time happens twice (fall back) | Uses the first occurrence, once only | 02:30 on 2027-10-31 is created once, at the earlier 02:30 |

The Review step notes such days. Only the creation time moves: the due date is a calendar date and is not changed by a clock change.

When a country changes its time rules

Governments sometimes change their clocks for good, for example Morocco, which moved to permanent GMT on 20 September 2026. RepeatWise follows the official time zone database (IANA) and applies such changes itself, even before Atlassian’s servers or your browser have them, so the schedule, the lists and the exports keep the same wall clock time. A schedule set for 09:00 in Casablanca runs at 09:00 Casablanca time.

Accuracy

The scheduler wakes up every 5 minutes. An issue is created within 5 minutes of its target time, not at the exact second. If Jira or the app is briefly unavailable, see Errors for retries and catch-up.