# Feature OP-18241 - Reducing Notification Flood Through Configurable Mention and Watcher Settings (In General, by Type, for childs)

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-18241

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| 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 | Modules and project features / Notification center |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As a** user who prefers fine-grained control over notifications  
**I want to** be able to individually enable or disable notifications for “mentioned” and “watcher” events, as well as configure them by work package type and child work packages,  
**so that** I have even more possibilities to customize my personal notification behavior and reduce unnecessary distractions.

**Acceptance criteria**

*   Users can toggle “Mentioned” notifications on/off in their personal notification settings.
    
*   Users can toggle “Watcher/Beobachter” notifications on/off in their personal notification settings.
    
*   Users can configure these settings **per work package type**.
    
*   Users can configure whether mentioned/watcher notifications should be sent for **child work packages**.
    
*   Default behavior remains unchanged unless the user actively changes their settings.
    
*   Toggling affects both:
    
    *   Email notifications
        
    *   In-app notifications
        
*   The UI clearly reflects the current configuration state for each option (enabled/disabled, type-specific, child WP rules).
    
*   When disabled, no notifications of that type are sent to the user.
    

**Technical notes**

*   Update backend notification dispatch logic
    
*   Extend the notification settings UI to show:
    
    *   Toggles for Mentioned / Watcher
        
    *   Type-specific configuration matrix (work package types × notification types)
        
    *   Toggle for child work package notifications
        
*   Ensure compatibility with existing notification categories and any REST API endpoints related to user settings.
    

**Permissions and visibility considerations**

*   _To whom is this feature visible?_
    
    *   All users with access to their personal notification settings.
        
*   _When is it not visible?_
    
    *   System administrators may enforce settings globally, but personal-level configuration should still override unless explicitly restricted.
        

**Translation considerations**

*   _Key terms and phrases in the key languages_
    

**Out of scope**

*   <br>
    

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
