# Feature MEET-577 - Allow history of meeting series to be output through ICS

Project: Stream Meetings
Status: new
URL: https://community.openproject.org/work_packages/MEET-577

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Use cases

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Build Number |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** a participant of a recurring meeting whose schedule has changed over its lifetime  
  

**I want to** see the complete history of all past occurrences in my calendar, including occurrences that belonged to earlier schedules (before the current schedule start)

**so that** I have an accurate and complete record of when the meeting actually took place across every schedule change, without past occurrences silently disappearing or being capped.

**Acceptance criteria**

*   OpenProject retains every historical schedule of a recurring meeting (each schedule era: frequency, interval, time of day, weekday, start and end), not only the current schedule.
    
*   The iCalendar export can represent occurrences from all previous schedules, not just the current schedule plus a bounded sliding window.
    
*   After a schedule edit, previously delivered occurrences remain visible in supported clients (Apple Calendar, OpenXchange / mailbox.org, Thunderbird, Google Calendar) with no duplicates and no orphaned &quot;ghost&quot; entries.
    
*   Editing a schedule never removes or duplicates occurrences already present in an attendee&#x27;s calendar.
    
*   Each historical occurrence keeps its actual date, time, location, attendees, and participation status as they were at the time.
    
*   Cancelled historical occurrences are represented consistently (either shown as cancelled or consistently omitted).
    
*   The representation is RFC 5545 / iTIP compliant and works through the email invite (Accept) flow, not only via file import or subscription feed.
    
*   No silent truncation: the number of exported historical occurrences is not artificially limited, or any limit is explicit and configurable.
    
*   Exporting a long-running series with many historical occurrences stays within acceptable performance bounds.
    

**Notes / context (why this is non-trivial)**

*   A single VEVENT carries one UID and one RRULE, and per RFC 5545 its DTSTART is the first instance. It therefore cannot express a schedule that changed frequency/time over time, and clients (OpenXchange in particular) reject RECURRENCE-ID overrides dated before the master DTSTART.
    
*   RDATE entries before the master DTSTART are silently ignored by Apple Calendar and OpenXchange, so they cannot carry history.
    
*   Emitting past occurrences as standalone events with their own UID renders on a fresh Accept, but on the schedule-edit transition (the only way previous-schedule occurrences arise) it produces duplicates/ghosts/errors across clients, because an occurrence that was already delivered as a series instance gets re-delivered under a new UID.
    
*   A correct implementation likely requires modelling each schedule era as its own bounded series (its own UID, RRULE with UNTIL) rather than a single evolving series, plus iTIP CANCEL handling for occurrences that move between eras. This is a substantial change and is the reason the current behaviour is limited to the current schedule.
