PM Calendar Overlay
Shows PM item due dates and sprint timelines on the Google Calendar panel alongside your real calendar events, read from a local mirror rather than fetched from the cloud. Events are color-coded by board, highlighted when overdue, and strictly read-only, with a one-click jump back into Mission Control and a show/hide block in the Calendar panel's own settings that turns the overlay on or narrows it to chosen projects.
On this page
What it is
Shows project due dates and sprint timelines on the Google Calendar panel alongside real calendar events -- read from the local SQLite mirror, not fetched from the cloud. PM items with date or timeline columns appear as calendar events alongside your Google Calendar entries.
Where to find it
On the Google Calendar panel, in the same views as your real Google events. Clicking a PM event opens the ordinary event popover; its PM branch shows the board name and an Open in PM button that navigates to the Mission Control virtual project.
Turning it on or off, and picking projects. Click the gear at the right edge of the Calendar panel's tab row. Under the "Calendars" list sits a Mission Control due dates block (shown while Mission Control is on):
- Show due dates — the switch that shows or hides every project's due dates on the calendar.
- Projects — one checkbox per project, shown while the switch is on. Checked means shown. All are checked until you uncheck one. The last checked project cannot be unchecked; use the switch to hide them all.
Changes save at once and the calendar redraws. These controls used to sit in Settings → Mission Control; they are not there any more. Searching Settings for "due dates" or "projects on the calendar" (or following a settings link to them) opens the Calendar with this panel open and the control highlighted.
How it behaves
Each PM event is color-coded by board (deterministic hash of board ID to one of 8 palette colors) and
highlighted when overdue (using the semantic --status-error-rgb token).
The overlay is read-only -- PM events have no Edit/Delete actions. The popover's PM branch also shows an overdue warning when applicable.
PM events are fetched in parallel with Google Calendar events (Promise.all). A PM fetch failure
degrades gracefully (empty array) and never breaks Google Calendar display.
Which items appear, and where they land
Date columns are matched by json_extract(value,'$.date') BETWEEN rangeStart AND rangeEnd. Timeline
columns use range overlap. The query filters to the visible calendar window in SQL, so the 500-row cap
bounds only in-window rows. Results are deterministically ordered.
Timelines extending beyond the visible window are clamped to [rangeStart, rangeEnd] so they don't
paint across adjacent months.
Settings
| Key | Type | Default | Effect |
|---|---|---|---|
pmCalendarOverlayEnabled |
boolean | true | Master toggle |
pmCalendarBoardIds |
string[] | [] | Empty = all boards; non-empty = filter |
Both require missionControlEnabled to be true. Their controls live in the Calendar panel's settings
popover (see "Where to find it"). Showing every project again stores [], so a project created later
appears automatically; while a narrower list is stored, a new project stays hidden until you check it.
The list holds up to 100 projects.
Related
The dates and timelines the overlay paints come from mission-control.md, the project-management system this panel reads from. If the items behind an entry are not what you expect, pm-my-work.md is the cross-board personal task view built on the same items, and pm-sprints.md explains the sprint timelines that show up here. Adding a date quickly from outside the board is covered by calendar-quick-add.md. Every page in this library is listed in INDEX.md.
Last verified 2026-10-17