Content
View differences
Updated by Niels Lindenthal almost 5 years ago
**As a** project member
**I want to** be able to view all notifications, keep track of new and older ones, filter them and flag work packages I want to come back to later
**so that** I can immediately, at a glance, understand which updates are the most relevant to me and require my attention.
**Note**
This Notification Center main view is related to Tasks <mention class="mention" data-id="38538" data-type="work_package" data-text="#38538">#38538</mention> and <mention class="mention" data-id="38538" data-type="work_package" data-text="#38538">#38538</mention> that deal with how the sidebar functions. This work package also overrides behaviour described in Feature <mention class="mention" data-id="38556" data-type="work_package" data-text="#38556">#38556</mention>, “Open split screen of first notification automatically” (since the split screen view is now on by default, and no notifications are selected automatically without user action).
**Visuals**
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/21991/content"></div></figure>
You can find the latest version of the mockup in [Figma](https://www.figma.com/file/54psSIYZuUgcyXrpGxHB1Z/Notification-Center-Main-View?node-id=47%3A591):
**Acceptance criteria**
* The notification list is organised by work packages; all notifications relating to the same work package are aggregated together and represent one single item in the list.
* By default, only work packages with unread notifications are displayed upon arriving at the Notification Center. (That is, the “Unread/All” filter toggle is set to “Unread”).
* Each notification will display these items (see mockup): Status; #ID; project name; reason for being notified (“responsible, mentioned, participating…”); type; subject; update preview (including type of update, by whom, and number of additional updates).
* The update preview will only list one update, even if the work package contains multiple notifications. This update will be in the format: “\[Event\] \[time of event\] by \[Author of update\] and \[n\] other updates”. _(The choice of which update to prioritise when there are multiple updates is currently being spec’d in this work package <mention class="mention" data-id="38584" data-type="work_package" data-text="#38584">#38584</mention>)._
* By default, when the user opens Notification Center, no notification is automatically selected; the split screen view is nevertheless displayed with an empty state. (_This empty state is out of scope for this work package and will be spec’d in a future work package)._
* If there are no unread notifications, both the notification list view and detailed view will show empty states _(out of scope of this work package, described in a future work package)._
* Clicking on a notification item selects it and displays the activity tab for that work package in the right-side view. _(The specificities of that screen will be spec’d in a future work package)._
* Unread notifications have one badge (with the number of unread notifications) and two actions (mark as read; switch flag/unflag) on the top-right corner.
* Read notifications have one action (switch flag/unflag) on the top-right corner (out of scope for this work package). corner.
* A notification is considered read in when it meets any of these conditions:
* When a user navigates away from that notification to another notification.
* When a user clicks on the “Mark as read” button in the notification item on the list.
* When the user clicks on "Mark All as Read" in the top bar.
* When a user clicks on the “Mark as read" button in the right-side detailed split-screen view _(Out of scope for this work package)._
* When a notification goes from unread to read, it looses the unread badge and the “mark as read button”. If the user has the “Unread” filter selected, the notification disappears immediately. If the user has the“All” filter selected, the notification will simply go from the “unread” visual style to the “read” visual style.
* Each time a notification is read, the unread count of total unread notifications is decremented by the number of unread notifications for that that work package.
* The view contains three filters: Unread/All (toggle), Project and Involvement. _(The first one \[Unread/Read\] has been implemented, but the other two are out of scope for this work package.)_
* The view contains one global action: _Mark all Mark All as read_. Read.
* New notifications that arrive after a user is already in the notification center are "popped in" asynchronously and take the top spot but do not change current selection (<mention class="mention" data-id="3" data-type="user" data-text="@Niels Lindenthal">@Niels Lindenthal</mention>: to be discussed).
**Out of Scope for this work package**
* The detailed view (right side of split screen) for notifications.
* The drop-down for the “Involvement” and “Project” filters.
* Each kind of update displayed in the notification item can be visually presented in slightly different ways depending on what information is most useful. For example, a change of status can be defined by an arrow going from the old status to a new; a new watcher added could be described with the “_\[thumbnail/name of person added\] was added as a watcher by \[thumbnail/name of person adding\]_”. This will be described in a future work package.
**Mockups in Figma**
All view: [https://www.figma.com/file/54psSIYZuUgcyXrpGxHB1Z/Notification-Center-Main-View?node-id=61%3A513](https://www.figma.com/file/54psSIYZuUgcyXrpGxHB1Z/Notification-Center-Main-View?node-id=61%3A513)
**I want to** be able to view all notifications, keep track of new and older ones, filter them and flag work packages I want to come back to later
**so that** I can immediately, at a glance, understand which updates are the most relevant to me and require my attention.
**Note**
This Notification Center main view is related to Tasks <mention class="mention" data-id="38538" data-type="work_package" data-text="#38538">#38538</mention> and <mention class="mention" data-id="38538" data-type="work_package" data-text="#38538">#38538</mention> that deal with how the sidebar functions. This work package also overrides behaviour described in Feature <mention class="mention" data-id="38556" data-type="work_package" data-text="#38556">#38556</mention>, “Open split screen of first notification automatically” (since the split screen view is now on by default, and no notifications are selected automatically without user action).
**Visuals**
<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/21991/content"></div></figure>
You can find the latest version of the mockup in [Figma](https://www.figma.com/file/54psSIYZuUgcyXrpGxHB1Z/Notification-Center-Main-View?node-id=47%3A591):
**Acceptance criteria**
* The notification list is organised by work packages; all notifications relating to the same work package are aggregated together and represent one single item in the list.
* By default, only work packages with unread notifications are displayed upon arriving at the Notification Center. (That is, the “Unread/All” filter toggle is set to “Unread”).
* Each notification will display these items (see mockup): Status; #ID; project name; reason for being notified (“responsible, mentioned, participating…”); type; subject; update preview (including type of update, by whom, and number of additional updates).
* The update preview will only list one update, even if the work package contains multiple notifications. This update will be in the format: “\[Event\] \[time of event\] by \[Author of update\] and \[n\] other updates”. _(The choice of which update to prioritise when there are multiple updates is currently being spec’d in this work package <mention class="mention" data-id="38584" data-type="work_package" data-text="#38584">#38584</mention>)._
* By default, when the user opens Notification Center, no notification is automatically selected; the split screen view is nevertheless displayed with an empty state. (_This empty state is out of scope for this work package and will be spec’d in a future work package)._
* If there are no unread notifications, both the notification list view and detailed view will show empty states _(out of scope of this work package, described in a future work package)._
* Clicking on a notification item selects it and displays the activity tab for that work package in the right-side view. _(The specificities of that screen will be spec’d in a future work package)._
* Unread notifications have one badge (with the number of unread notifications) and two actions (mark as read; switch flag/unflag) on the top-right corner.
* Read notifications have one action (switch flag/unflag) on the top-right corner (out of scope for this work package).
* A notification is considered read in when it meets any of these conditions:
* When a user navigates away from that notification to another notification.
* When a user clicks on the “Mark as read” button in the notification item on the list.
* When the user clicks on "Mark All as Read" in the top bar.
* When a user clicks on the “Mark as read" button in the right-side detailed split-screen view _(Out of scope for this work package)._
* When a notification goes from unread to read, it looses the unread badge and the “mark as read button”. If the user has the “Unread” filter selected, the notification disappears immediately. If the user has the“All” filter selected, the notification will simply go from the “unread” visual style to the “read” visual style.
* Each time a notification is read, the unread count of total unread notifications is decremented by the number of unread notifications for that that work package.
* The view contains three filters: Unread/All (toggle), Project and Involvement. _(The first one \[Unread/Read\] has been implemented, but the other two are out of scope for this work package.)_
* The view contains one global action: _Mark all
* New notifications that arrive after a user is already in the notification center are "popped in" asynchronously and take the top spot but do not change current selection (<mention class="mention" data-id="3" data-type="user" data-text="@Niels Lindenthal">@Niels Lindenthal</mention>: to be discussed).
**Out of Scope for this work package**
* The detailed view (right side of split screen) for notifications.
* The drop-down for the “Involvement” and “Project” filters.
* Each kind of update displayed in the notification item can be visually presented in slightly different ways depending on what information is most useful. For example, a change of status can be defined by an arrow going from the old status to a new; a new watcher added could be described with the “_\[thumbnail/name of person added\] was added as a watcher by \[thumbnail/name of person adding\]_”. This will be described in a future work package.
**Mockups in Figma**