[Task] Audit scheduling#1 reminder checklist against current implementation #3

New Issue

zemion · 2026-07-14T20:09:35+02:00

zemion commented

2026-07-14 20:09:35 +02:00

Problem / User Need

govoplan-scheduling#1 is already closed, but new reminder notes were added about Terminfindung/schedule-poll behavior. We need an explicit open work item to compare those reminders with the current implementation and decide what is done, still open, or obsolete.

Checklist To Reconcile

Check terminplaner.dfn.de, Doodle, and similar tools as UX/reference behavior.
Select days and timeslots.
Allow yes / no / maybe answers.
Allow or disallow multiple answers.
Select participants, internal and external.
Alternatively share a public link; this should work without access, with limited functionality.
For internal participants, check calendars for collisions when calendar is present/enabled.
Block out timeslots in the organizer's calendar(s).
Wait for participant answers.
Send reminders to participants who have not answered yet.
Decide on the final option.
Send out VEVENT once decided.
Free alternative blockers and create/update the final calendar event.

Acceptance Criteria

Each checklist item is classified as implemented, still open, or obsolete.
Implemented items are linked to code/tests or existing issues where possible.
Still-open items are split into focused follow-up issues or added to an existing issue with clear acceptance criteria.
Obsolete items are documented with the reason they no longer apply.
govoplan-scheduling#1 remains a historical boundary issue; this issue owns the follow-up audit.

## Problem / User Need `govoplan-scheduling#1` is already closed, but new reminder notes were added about Terminfindung/schedule-poll behavior. We need an explicit open work item to compare those reminders with the current implementation and decide what is done, still open, or obsolete. ## Checklist To Reconcile - Check `terminplaner.dfn.de`, Doodle, and similar tools as UX/reference behavior. - Select days and timeslots. - Allow yes / no / maybe answers. - Allow or disallow multiple answers. - Select participants, internal and external. - Alternatively share a public link; this should work without access, with limited functionality. - For internal participants, check calendars for collisions when calendar is present/enabled. - Block out timeslots in the organizer's calendar(s). - Wait for participant answers. - Send reminders to participants who have not answered yet. - Decide on the final option. - Send out VEVENT once decided. - Free alternative blockers and create/update the final calendar event. ## Acceptance Criteria - Each checklist item is classified as implemented, still open, or obsolete. - Implemented items are linked to code/tests or existing issues where possible. - Still-open items are split into focused follow-up issues or added to an existing issue with clear acceptance criteria. - Obsolete items are documented with the reason they no longer apply. - `govoplan-scheduling#1` remains a historical boundary issue; this issue owns the follow-up audit.

zemion added the