Content
View differences
Updated by Oliver Günther 14 days ago
**As** a Project Manager
**I want to** schedule recurring meetings by “nth weekday of month” (e.g., _first Tuesday_, _last Friday_, _second Wednesday_)
**so that** I can align meetings with stakeholder availability and reporting cycles that follow calendar patterns rather than fixed day/week intervals.
**Acceptance criteria**
* Add monhtly scheduling options for meeting series
* "Every month on the 1st"
* "The first work day of every month
* "Every month on the 16th"
* User can choose:
* **Ordinal**: first, second, third, fourth, last.
* **Weekday**: Monday–Sunday.
* Optional: Optional scope: “Every n months” (default 1).
* When the scheduled start time does not match the computed first occurrence, the caption will be extended to state: "The first occurrence of this series will be on <date/time>"
<img class="image_resized op-uc-image op-uc-image_inline" style="width:361px;" src="/api/v3/attachments/319472/content">
**Technical notes**
* **Recurrence model**: Extend recurrence logic to support iCalendar RRULE equivalents:
* `FREQ=MONTHLY;BYDAY=TU;BYSETPOS=1` → first Tuesday.
* `FREQ=MONTHLY;BYDAY=FR;BYSETPOS=-1` → last Friday.
* Add optional `INTERVAL=n` for “every n months”.
**Permissions and visibility considerations**
* **To whom is this feature visible?**
* All users who can create or edit meetings within a project (same as existing recurring meetings), and all users who can view meetings will see the generated occurrences.
* **When is it not visible?**
* Users without meeting permissions won’t see recurrence controls.
* Hidden if the instance is a single meeting (no series).
**Translation considerations**
* **Suggestions for key terms and phrases in the key languages**
* EN: “Monthly by pattern (nth weekday)”, “first/second/third/fourth/last”, “weekday”, “Every n months”, “Preview next 3 occurrences”
* DE: „Monatlich nach Muster (n-ter Wochentag)“, „erster/zweiter/dritter/vierter/letzter“, „Wochentag“, „Alle n Monate“, „Vorschau der nächsten 3 Termine“
* FR: « Mensuel par modèle (nième jour de semaine) », « premier/deuxième/troisième/quatrième/dernier », « jour de semaine », « Tous les n mois », « Aperçu des 3 prochaines occurrences »
* ES: « Mensual por patrón (n-ésimo día de la semana) », « primero/segundo/tercero/cuarto/último », « día de la semana », « Cada n meses », « Vista previa de las próximas 3 ocurrencias »
**Out of scope**
* Arbitrary complex rules beyond monthly nth-weekday (e.g., “first business day”, “every weekday”, “every M/W/F”, “skip public holidays with auto-shift”).
* Organization-wide holiday calendars and automatic date shifting.
* Bulk retroactive changes to past occurrences without explicit selection.
* Cross-project series linking.
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
<br>
<br>
**I want to** schedule recurring meetings by “nth weekday of month” (e.g., _first Tuesday_, _last Friday_, _second Wednesday_)
**so that** I can align meetings with stakeholder availability and reporting cycles that follow calendar patterns rather than fixed day/week intervals.
**Acceptance criteria**
* Add monhtly scheduling options for meeting series
* "Every month on the 1st"
* "The first work day of every month
* "Every month on the 16th"
* User can choose:
* **Ordinal**: first, second, third, fourth, last.
* **Weekday**: Monday–Sunday.
* Optional:
* When the scheduled start time does not match the computed first occurrence, the caption will be extended to state: "The first occurrence of this series will be on <date/time>"
<img class="image_resized op-uc-image op-uc-image_inline" style="width:361px;" src="/api/v3/attachments/319472/content">
**Technical notes**
* **Recurrence model**: Extend recurrence logic to support iCalendar RRULE equivalents:
* `FREQ=MONTHLY;BYDAY=TU;BYSETPOS=1` → first Tuesday.
* `FREQ=MONTHLY;BYDAY=FR;BYSETPOS=-1` → last Friday.
* Add optional `INTERVAL=n` for “every n months”.
**Permissions and visibility considerations**
* **To whom is this feature visible?**
* All users who can create or edit meetings within a project (same as existing recurring meetings), and all users who can view meetings will see the generated occurrences.
* **When is it not visible?**
* Users without meeting permissions won’t see recurrence controls.
* Hidden if the instance is a single meeting (no series).
**Translation considerations**
* **Suggestions for key terms and phrases in the key languages**
* EN: “Monthly by pattern (nth weekday)”, “first/second/third/fourth/last”, “weekday”, “Every n months”, “Preview next 3 occurrences”
* DE: „Monatlich nach Muster (n-ter Wochentag)“, „erster/zweiter/dritter/vierter/letzter“, „Wochentag“, „Alle n Monate“, „Vorschau der nächsten 3 Termine“
* FR: « Mensuel par modèle (nième jour de semaine) », « premier/deuxième/troisième/quatrième/dernier », « jour de semaine », « Tous les n mois », « Aperçu des 3 prochaines occurrences »
* ES: « Mensual por patrón (n-ésimo día de la semana) », « primero/segundo/tercero/cuarto/último », « día de la semana », « Cada n meses », « Vista previa de las próximas 3 ocurrencias »
**Out of scope**
* Arbitrary complex rules beyond monthly nth-weekday (e.g., “first business day”, “every weekday”, “every M/W/F”, “skip public holidays with auto-shift”).
* Organization-wide holiday calendars and automatic date shifting.
* Bulk retroactive changes to past occurrences without explicit selection.
* Cross-project series linking.
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
<br>
<br>