Content
View differences
Updated by Marc Alcobé 3 months ago
**As a** tablet user **As** a \[enter role of OpenProject user\]
**I want** to review and manage my notifications using a split-view layout want to** \[enter objective\]
**so that** I can quickly process updates, respond to changes, and stay informed without repeatedly navigating between lists and details. \[enter desired result\]
**Acceptance criteria**
* When displayed on a tablet in landscape orientation, the Notifications module uses a **master–detail layout**:
* **Left pane**:
* Notification list
* Filters (Unread / All)
* Inbox selector
* Search input
* Settings access (new to the view): Should open the notification settings inside the user account
* **Right pane**:
* Details of the work package on the activity tab of the selected notification
* Selecting a notification in the list updates the detail pane without navigating away from the list.
* Users can:
* Mark individual notifications as read
* Using the three dots menu
* Or the swipe behaviour
* Mark all notifications as read
* The notification detail view displays the same as a work package but opened through the activity tab and scrolling to the activity that triggered the notification.
* Actions taken in the detail pane update the notification state in the list. <br>
**Technical notes**
* The tablet Notifications layout is enabled at the tablet breakpoint: 900px.
* On phones or tablets in portrait orientation, the phone Notifications layout is used.
* The list and detail panes are rendered independently.
* Notification read/unread state is synced in real time.
* The detail pane supports vertical scrolling independently from the list pane.
* Filters and inbox selection apply only to the left pane. <br>
**Permissions and visibility considerations**
* Notifications only include events related to:
* Projects
* Work packages
the user has permission to view.
* Activity details respect the user’s permissions on the underlying resource. _To whom is this feature visible?_
* Actions in the detail pane are only available if the user has permission. _When is it not visible?_
**Translation considerations**
* Only one string is added _Key terms and phrases in the tablet version:
* Settings
key languages_
**Out of scope**
* Portrait-optimized tablet layout <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want** to review and manage my notifications using a split-view layout
**so that** I can quickly process updates, respond to changes, and stay informed without repeatedly navigating between lists and details.
**Acceptance criteria**
* When displayed on a tablet in landscape orientation, the Notifications module uses a **master–detail layout**:
* **Left pane**:
* Notification list
* Filters (Unread / All)
* Inbox selector
* Search input
* Settings access (new to the view): Should open the notification settings inside the user account
* **Right pane**:
* Details of the work package on the activity tab of the selected notification
* Selecting a notification in the list updates the detail pane without navigating away from the list.
* Users can:
* Mark individual notifications as read
* Using the three dots menu
* Or the swipe behaviour
* Mark all notifications as read
* The notification detail view displays the same as a work package but opened through the activity tab and scrolling to the activity that triggered the notification.
* Actions taken in the detail pane update the notification state in the list.
**Technical notes**
* The tablet Notifications layout is enabled at the tablet breakpoint: 900px.
* On phones or tablets in portrait orientation, the phone Notifications layout is used.
* The list and detail panes are rendered independently.
* Notification read/unread state is synced in real time.
* The detail pane supports vertical scrolling independently from the list pane.
* Filters and inbox selection apply only to the left pane.
**Permissions and visibility considerations**
* Notifications only include events related to:
* Projects
* Work packages
the user has permission to view.
* Activity details respect the user’s permissions on the underlying resource.
* Actions in the detail pane are only available if the user has permission.
**Translation considerations**
* Only one string is added
* Settings
* Portrait-optimized tablet layout
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._