# Feature MEET-387 - Debounce emails for meetings

Project: Stream Meetings
Status: closed
URL: https://community.openproject.org/work_packages/MEET-387

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Low |
| Target versions | 17.5.0 |
| 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 / Meetings |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Oliver Günther |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** an organizer of meetings in OpenProject  
**I want to** aggregate multiple changes I've made into one email  
**so that** prevent subsequent updates (e.g., invites) causing multiple emails to the same set of people

**Acceptance criteria**

  - Apply a debounce of one minute to any updates and invitation changes of a meeting or occurrence

  - The debounce does not apply when the meeting is deleted (one-time action)

  - Any changes to the meeting by any user with appropriate permission triggers the debounce job
    
      - Any subsequent changes are being respected by taking into consideration any journal changes starting with an initial journal.

  - Remove the "Participant added" and "Participant removed" emails in favor of a generic updated email, listing the new and removed participants. This avoid sending multiple emails if the schedule changes AND participants change while at it
    
    <br>

**Technical notes**

  - 
    <br>

**Permissions and visibility considerations**

  - *No changes*

**Translation considerations**

  - *None*

**Out of scope**

  - 
    <br>

*Set the* **To be informed/consulted teams** *field to include all teams necessary to be informed of the changes.*