Content
View differences
Updated by Marc Alcobé about 15 hours ago
**As a** user viewing **As** a work package \[enter role of user\]
**I want** a “Meetings” tab that shows all meetings where this work package appears as an agenda item want to** \[enter objective\]
**so that** I can quickly understand where it was discussed and open the relevant meeting. \[enter desired result\]
### Acceptance Criteria **Acceptance criteria**
* The Work Package detail screen includes a new **Meetings** tab.
<br>
**Technical notes**
* The Meetings tab supports two states:
* **Empty state (Upcoming):** When the work package is not scheduled in any upcoming meeting agenda, show the empty illustration <br>
**Permissions and message (per mockup).
visibility considerations**
* **Empty state (Past):** When the work package was not part of any past meeting agenda, show the empty illustration and message (per mockup).
* The Meetings tab shows a segmented control:
* **Upcoming**
* **Past**
* In **Upcoming**, the list contains all upcoming meeting occurrences where the work package _To whom is included as an agenda item. this feature visible?_
* In **Past**, the list contains all past meeting occurrences where the work package was included as an agenda item.
* Each list item displays meeting information (per mockup), including at minimum:
* Recurrence hint (e.g., “Every working day”, “Every week”) if available
* Meeting occurrence date/time
* Meeting series title (e.g., “UX Design Daily”)
* The agenda item snippet/notes associated with the work package (if available)
* Meeting metadata such as presenter and time (if available in the agenda item)
* If the agenda item contains **Outcomes**, show them within the list item, including:
* Outcome title (e.g., “Outcome 1”)
* Outcome content preview
* Tapping a meeting row in the list **opens the meeting occurrence**.
* If supported, the meeting opens scrolled to the agenda item for the current work package visible/selected/scrolled into view.
* If not supported, the meeting opens normally, and the agenda item remains discoverable in the meeting agenda.
* If the user lacks access to a meeting (permissions), that meeting _When is it not shown in the list.
* The list is ordered:
* Upcoming: ascending by start datetime (soonest first)
* Past: descending by start datetime (most recent first)
* Loading states are handled:
* While loading, show a loading state skeleton.
* On error, show an error state with a retry action.
### Technical Notes
* <br> visible?_
### Permissions and Visibility Considerations **Translation considerations**
* A meeting appears in the list only if the user has permission to view:
* the meeting occurrence, _Key terms and
* the agenda item content (notes/outcomes)
* If the user can see the meeting but not the agenda item details hide that meeting row entirely, or show the meeting row but omit agenda-item details (must align with existing permission patterns).
* Presenter identity visibility follows the same rules as user visibility elsewhere phrases in the desktop product.
* If the work package itself is visible but the meeting is not, do not expose meeting title/date via this tab. key languages_
### Translation Considerations **Out of scope**
* Localize:
* Empty state messages
* Error messages and retry labels
### Out <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of Scope
* Editing meetings or agenda items from within the Work Package Meetings tab (e.g., adding/removing the work package, editing notes/outcomes). changes._
**I want** a “Meetings” tab that shows all meetings where this work package appears as an agenda item
**so that** I can quickly understand where it was discussed and open the relevant meeting.
### Acceptance Criteria
* The Work Package detail screen includes a new **Meetings** tab.
**Technical notes**
* **Empty state (Upcoming):** When the work package is not scheduled in any upcoming meeting agenda, show the empty illustration
**Permissions
* The Meetings tab shows a segmented control:
* **Upcoming**
* **Past**
* In **Upcoming**, the list contains all upcoming meeting occurrences where the work package
* In **Past**, the list contains all past meeting occurrences where the work package was included as an agenda item.
* Each list item displays meeting information (per mockup), including at minimum:
* Recurrence hint (e.g., “Every working day”, “Every week”) if available
* Meeting occurrence date/time
* Meeting series title (e.g., “UX Design Daily”)
* The agenda item snippet/notes associated with the work package (if available)
* Meeting metadata such as presenter and time (if available in the agenda item)
* If the agenda item contains **Outcomes**, show them within the list item, including:
* Outcome title (e.g., “Outcome 1”)
* Outcome content preview
* Tapping a meeting row in the list **opens the meeting occurrence**.
* If supported, the meeting opens scrolled to the agenda item for the current work package visible/selected/scrolled into view.
* If not supported, the meeting opens normally, and the agenda item remains discoverable in the meeting agenda.
* If the user lacks access to a meeting (permissions), that meeting
* The list is ordered:
* Upcoming: ascending by start datetime (soonest first)
* Past: descending by start datetime (most recent first)
* Loading states are handled:
* While loading, show a loading state skeleton.
* On error, show an error state with a retry action.
### Technical Notes
* <br>
### Permissions and Visibility Considerations
* A meeting appears in the list only if the user has permission to view:
* the meeting occurrence,
* the agenda item content (notes/outcomes)
* If the user can see the meeting but not the agenda item details hide that meeting row entirely, or show the meeting row but omit agenda-item details (must align with existing permission patterns).
* Presenter identity visibility follows the same rules as user visibility elsewhere
* If the work package itself is visible but the meeting is not, do not expose meeting title/date via this tab.
### Translation Considerations
* Localize:
* Empty state messages
* Error messages and retry labels
### Out
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed
* Editing meetings or agenda items from within the Work Package Meetings tab (e.g., adding/removing the work package, editing notes/outcomes).