# Feature COMMS-6 - Project filter in Inbox view in notification center

Project: Stream Communicator
Status: rejected
URL: https://community.openproject.org/work_packages/COMMS-6

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Niels Lindenthal |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As a** project member  
**I want to** filter my unread notifications by project  
**so that** identify and access the most relevant notifications quickly, especially when I am organising my workflow by project.

**Note**   
This builds on the filters that were out of scope for work package <mention class="mention" data-id="38592" data-type="work_package" data-text="#38592">\#38592</mention> concerning the Main List view.

**Visuals**   
*Visual 1: Project Filter*

<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/22079/content"></div></figure>

**Acceptance Criteria**

  - Besides unread/all (already implemented), there is one other filter  available to users in the "Inbox" view in notification center: "Project".

  - By default, the project filter is inactive (i.e, notifications from all projects are displayed by default).

  - When the filter is inactive, it will simply read "Filter by Project".

  - When the user clicks on the Project dropdown list, they are afforded the ability to select individual projects (including sub-projects) via a list of checkboxes that represent existing project hierarchies (much like the drop-down that is displayed when clicking on "Projects" in the top-left corner of the screen today).

  - The user can select as many or as few projects as they please.
    
      - Zero selections mean the filter remains inactive.
    
      - If only one project is selected, the filter title is the name of the project, truncated to the maximum length permitted by this filter dropdown element.
    
      - If two or more projects are selected, the title should be "\[n\] projects" where n = number of projects selected.

  - The drop down as an "active" state (blue) which is visually distinct from the inactive state.

  - The project filter also has a search box that functions the same as the search box that is currently implemented to browse projects.

  - There is an "Apply" button that applies the filter. Until this button is clicked, the filters are not applied. *(Note: behaviour to be confirmed, needs discussion, should we consider what clicking outside the dialog does).*

  - The list of projects is scrollable; its height should be limited to ensure that the "Apply" button is visible to the user in their viewport without having to scroll.

  - The filter has a "Clear selection" button that deselects all current project selections. *(Note for discussion: does the button automatically clear the selection and apply the no selection? Or will the user then have to click on Apply?)*

  - The filter selection is applied asynchronously and does not necessitate a refresh.

**Mockups in Figma**   
Link to relevant mockups in Figma:   
\- Project filter: <https://www.figma.com/file/54psSIYZuUgcyXrpGxHB1Z/Notification-Center-Main-View?node-id=90%3A2719>