The app sends reminders on a schedule, so it needs its own access to Slack and Tempo. Only Jira admins can open this tab. Connect Slack opens Slack: pick the workspace, press Allow, come back.

Tempo needs one extra step, because a Tempo OAuth application belongs to the site it was created in: a wizard links to the right Tempo screen, shows the redirect URI to copy, and takes the client ID and secret it generates. Then Connect Tempo → Authorize — as somebody who may see everybody's worklogs, or the rest will look like they never logged time.

Test connections checks both; a rejected by badge means the access was revoked.

Working days to check is the window: the last N working days, each checked separately, so an empty day counts even if the rest of the week is full.

Acceptable days of delay forgives the freshest days of that window. The default of 1 means today is never asked about, because the time for it may still be coming.

Run times and Manager run times are two independent schedules, comma-separated, on a 24-hour clock in UTC; an empty list switches that mailing off. The app wakes up once an hour, so a check starts at the top of the hour following the time you set. Under the fields it shows the current time and when the next run is due. read it after every change.

The rest of the tab is the message texts: the personal reminder, the manager digest, the day-by-day detailed report and the all-clear a manager gets when their whole team is done. Each takes placeholders `{name}`, `{missing}`, `{days}`, `{from}`, `{to}` are listed under the field itself.

Fields save when you leave them; there is no Save button.

A holiday is not a working day: nobody has to log time for it, and the scheduled check does not run on it either. The two switches at the top decide what counts as a day off: skipping weekends, and taking the holiday calendar into account and both save the moment you flip them. With the calendar switched off the list below changes nothing, and holidays become ordinary working days.

Holidays are stored as rules, not dates, so the calendar does not go stale: "last Monday of May" is still the right Monday next year. Add holiday asks for a name and how it repeats - a fixed day of a month, or the n-th weekday of a month.
Restore defaults brings back the shipped calendar, and Remove selected clears the ones you tick.

The shift in days field is for days that hang off another holiday. The day after Thanksgiving is "4th Thursday of November, plus one day" not the 4th Friday, which in some years is a different date altogether.

A day covered by a vacation is not a debt: it is dropped from that person's missing days, so neither they nor their manager is asked about it. Two switches control this — whether the calendar is used

at all, and whether to hold back the direct message while a person is on leave. The second only silences the DM; the person still appears in their manager's digest, so the days are not forgotten.

Vacations come from a calendar you publish as a read-only feed: in Google Calendar, open the calendar's Settings → Integrate calendar and copy the Secret address in iCal format. Anyone

with that link can read the calendar, so it is kept in Forge's encrypted storage and never shown back. Google serves the feed from a cache, so a vacation entered minutes ago may take a while to

appear.

Test calendar reads the feed and shows how event titles line up with your tracked users. Somebody spelled differently in the calendar than in Jira comes back as "no match" — the fix is the

Name in the vacation calendar column on the Users tab.

This tab runs exactly the same check as the schedule, but immediately, and it does send real messages: a Slack DM to every tracked user missing time in the window, digests or all-clear notes

to every manager, and a detailed report for each person who has recipients in that column. A manual run ignores the schedules, the weekday-only rule and the once-per-day limit, so it will send again

even if the same reminders went out an hour ago. That is why it asks for confirmation first, naming how many people are about to be messaged.

If Slack or Tempo is not connected, or nobody is tracked yet, the tab says so instead of running — there is nothing to check. While a run is in progress it shows its own progress; the run happens on the server, so you can leave the page and come back to it.

Underneath is the report of the most recent run, scheduled or manual, and it is the best place to answer "why did nothing arrive": who was reminded, who was clear, who was on leave, and anybody the app could not reach — each with the reason.