Eriksen Labs Support
Documentation

Repeating on a schedule

v3.5.03 min readUpdated

Choose Repeat on a schedule and fill in the form:

  • Name it — how it appears in your list. Defaults to the request's summary.
  • How often — once on a date, every day, every week, every month, or quarterly (every 3 months). Repeat every multiplies the day, week or month: every 2 weeks, every 6 months, and so on.
  • On — for a monthly or quarterly schedule, which day of the month. The same day as the first one repeats the date you pick, as before. You can also choose a day of the month (1 to 31, or the last day), a weekday such as the first Monday or the last Friday, or a working day such as the second. Working days are Monday to Friday.
  • For a weekly schedule, On can also be Chosen days of the week: tick the days, such as Monday and Thursday, and it repeats on them every week. This appears when your project's shortest gap between repeats is 3 days or less. When it does not, the form says why.
  • First one on (Starting from with a pattern), and at — the date and time of the first request, which must be in the future. With a pattern, the first request is the first matching day on or after that date.
  • Stop after this many — leave blank to keep going until the limit your administrator set.

See the dates before you save. Under the form, When it runs lists the next dates, up to five, in your time zone, and says when the schedule stops: after the number you set, or on your project's limit. If the form would be refused, for example because it repeats more often than your project allows, it says so there instead.

Days the service desk is closed. Your service desk can mark days as closed, such as public holidays. A request due on one goes out at the same time on the next open day, Monday to Friday, or is skipped, as the desk has chosen. The preview shows which, for example Mon 28 Dec 09:00 (25 Dec: the desk is closed).

Times are yours, not the server's. The app reads your timezone from your browser and shows it under the time picker. A schedule set for 09:00 stays at 09:00 after the clocks change, rather than drifting by an hour.

Monthly dates behave sensibly. A schedule anchored on the 31st falls back to the 28th in February and returns to the 31st in March — it does not stay stuck on the earlier day for the rest of the year.

A schedule that has been paused does not catch up. Resuming moves it to the next occurrence in the future. Six missed months do not arrive at once.

Schedules use no Automation steps. They run inside the app, not as Jira Automation flows. Flows of your own that run when a request is created still run, and count, as they would for a request typed by hand. What the same schedules would cost as flows from 3 December 2026 is in our guide to recurring tickets after step billing.

Timing

Scheduled requests are raised within a few minutes of the time you chose, not to the second. If you need something to exist before a particular deadline, set it for the morning rather than the minute.