Content
View differences
Updated by Marc Alcobé about 15 hours ago
**As a** meeting organizer **As** a \[enter role of user\]
**I want to** edit a meeting series template that defines the structure of meetings in that series (sections, agenda items, participants, etc.) \[enter objective\]
**so that** future meetings in the series open with a consistent, up-to-date format without changing historical meetings. \[enter desired result\]
### Acceptance Criteria **Acceptance criteria**
* The meeting series details screen provides a dropdown menu action **“Edit series template”**.
<br>
**Technical notes**
* Tapping **“Edit series template”** opens the **Meeting Series Template** editor for the selected series.
<br>
**Permissions and visibility considerations**
* The template editor clearly indicates in a banner the user _To whom is editing a template for a meeting series and that **new occurrences will use this template**. feature visible?_
* The template editor supports configuring the meeting “opening structure”, including:
* Sections displayed when a meeting _When is opened.
it not visible?_
**Translation considerations**
* The order of those sections.
* The ability to add new section entries/items.
* All the existing feature patterns as a meeting agenda.
* On top of the agenda the users can also add the **Details**, **Participants** _Key terms and **Attachments** present phrases in all the future meetings key languages_
**Out of the series
* Changes made in the template editor are saved and persist for the series.
* **Template changes apply only to future meetings in the series**:
* Meetings that are already in the **Past** list keep their existing structure and content.
* Meetings that have already occurred do not get their sections/items/participants retroactively modified.
* After editing, newly created/opened future meetings in the series reflect the updated template.
* If saving fails (network/server), the user sees an error state and can retry without losing edits (where feasible).
### Technical Notes scope**
* <br>
### Permissions and Visibility Considerations
* Only users with permission _Set the_ **To be informed/consulted teams** _field to manage the meeting series (e.g., organiser/owner or appropriate project role) can edit the series template.
* Users without permission:
* Do not see **“Edit series template”** in the overflow menu.
* If a meeting series belongs include all teams necessary to a project, enforce project-level role checks consistently (view vs edit).
### Translation Considerations
* Localize all user-facing strings, including:
* “Edit series template”
* Informational banner text (e.g., “You are editing a template… Future meetings will use this template.”)
* Section UI labels, save/discard prompts, error messages
### Out be informed of Scope
* Retroactively updating past meetings in the series based on the new template.
* Advanced template version management UI (e.g., version history, restore previous version, diff view). changes._
**I want to** edit a meeting series template that defines the structure of meetings in that series (sections, agenda items, participants, etc.)
**so that** future meetings in the series open with a consistent, up-to-date format without changing historical meetings.
### Acceptance Criteria
* The meeting series details screen provides a dropdown menu action **“Edit series template”**.
**Technical notes**
**Permissions and visibility considerations**
* The template editor supports configuring the meeting “opening structure”, including:
* Sections displayed when a meeting
**Translation considerations**
* The ability to add new section entries/items.
* All the existing feature patterns as a meeting agenda.
* On top of the agenda the users can also add the **Details**, **Participants**
**Out
* Changes made in the template editor are saved and persist for the series.
* **Template changes apply only to future meetings in the series**:
* Meetings that are already in the **Past** list keep their existing structure and content.
* Meetings that have already occurred do not get their sections/items/participants retroactively modified.
* After editing, newly created/opened future meetings in the series reflect the updated template.
* If saving fails (network/server), the user sees an error state and can retry without losing edits (where feasible).
### Technical Notes
* <br>
### Permissions and Visibility Considerations
* Only users with permission
* Users without permission:
* Do not see **“Edit series template”** in the overflow menu.
* If a meeting series belongs
### Translation Considerations
* Localize all user-facing strings, including:
* “Edit series template”
* Informational banner text (e.g., “You are editing a template… Future meetings will use this template.”)
* Section UI labels, save/discard prompts, error messages
### Out
* Retroactively updating past meetings in the series based on the new template.
* Advanced template version management UI (e.g., version history, restore previous version, diff view).