Closed days
In Project settings → Apps → Recurring requests, under Closed days, mark the days your service desk is closed, such as public holidays: click a date on the calendar to close it, and click it again to open it. Then choose Save settings. A project can keep up to 200 closed days, up to five years ahead. A closed day is removed a month after its date, the next time the closed days are changed and saved.
When a recurring request is due on a closed day
- Move to the next open day (the default) — it goes out on the next Monday to Friday that is not closed, at the same time. A run never moves earlier, and a move never adds one: if the next open day would reach the schedule's following run, that run is skipped instead. A request set up to run once always moves.
- Skip that run — nothing is raised for that date, and the schedule carries on from its next run.
Each schedule is checked against its own date, the one its customer sees, so a closed 25 December is 25 December wherever the customer is. A working-day pattern counts Monday to Friday with closed days included, so a run it picks on a closed day is moved or skipped like any other.
Saving moves the next run of any schedule that falls on a closed day, and brings back a run that was moved or skipped because of a day you open again, while that day is still ahead. Nothing is raised by saving. If some schedules cannot be updated at that moment, the page says so and offers Update next runs, and the app also updates them in the background shortly after.
A moved run can come closer to the next one than the shortest gap between repeats: a monthly run moved from 16 February to the 17th is 27 days before the next one. The shortest gap applies to the repeat the customer chooses, not to a single moved run.