REQ-FUN-114
Schedule export in iCalendar (ICS) and CSV formats
What
System SHALL provide GET /v1/projects/{id}/schedule/export?format=ics and format=csv endpoints that emit the project's activities (and milestones from the plan_step table) as RFC 5545 iCalendar events and as CSV rows respectively.
Why
Human users want their schedule in their calendar tool. CSV supports downstream spreadsheet analysis. established project management guidelines Communications Management calls for stakeholder-appropriate reporting formats.
How
ICS event per activity with VEVENT(uid=activity:{id}, dtstart=planned_start, dtend=planned_finish, summary=activity.name, description=activity.description, categories=critical_path|standard). CSV columns: id, name, work_package, planned_start, planned_finish, status, percent_complete, on_critical_path.
Done when
An ICS export imports cleanly into a reference calendar app; CSV round-trips via a downstream test importer; both formats reflect the latest schedule state at export time.
Out of scope
Bi-directional sync (read-only export); recurring events.
established project management guidelines Mapping
Stakeholder-friendly distribution of schedule data per Communications Management.