Content
View differences
Updated by Oliver Günther over 1 year ago
**As** a user of meeting series in OpenProject
**I want to** have a stable URL to link to the meeting series and its next iteration
**so that** I can embed this into the calendar
**Acceptance criteria**
* Meeting series index pages have a fixed url:
* Format: `{/projects/identifier}/recurring_meetings/{id}-{slug}`
* with slug, "/projects/openproject/recurring\_meetings/232-product-weekly"
* without slug, "/projects/openproject/recurring\_meetings/232"
* There is a route below magic link that always links to the _next iteration_ of the meeting
* Format: `/recurring_meetings/{id}/occurences/next`
`{/projects/identifier}/recurring_meetings/{id}-{slug}/next`
* There is a route that refers to the given time iteration of the meeting
with slug, "/projects/openproject/recurring\_meetings/232-product-weekly/next"
* Format: `/recurring_meetings/{id}}/occurrences/DATE` without slug, "/projects/openproject/recurring\_meetings/232/next"
The second one is used in the ICS download to refer to schedules **Open**
* Additional entry points for calendar entries, so that are you do not yet instantiated.
only see the next iteration, but also the previous one
<br>
**I want to** have a stable URL to link to the meeting series and its next iteration
**so that** I can embed this into the calendar
**Acceptance criteria**
*
* Format: `{/projects/identifier}/recurring_meetings/{id}-{slug}`
* with slug, "/projects/openproject/recurring\_meetings/232-product-weekly"
* without slug, "/projects/openproject/recurring\_meetings/232"
*
* Format: `/recurring_meetings/{id}/occurences/next`
The second one is used in the ICS download to refer to schedules
* Additional entry points for calendar entries, so