# Feature MEET-39 - Meetings: Notify users that the page has been updated and incite a reload

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

## Planning

| Attribute | Value |
| --- | --- |
| Date | 2024-07-10 – 2024-08-28 |
| Priority | Medium |
| Target versions | 14.6.0 |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

| ID | Subject | Status | Decision |
| --- | --- | --- | --- |
| MEET-54 | Should dismissing the flash banner stop update polling forever? | decided | The flash banner will not be dismissible |
| MEET-60 | Which actions should trigger the flash? | decided |  |
| MEET-78 | How should reordering of sections act on the flash notification | rejected |  |

## Use cases

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| MEET-64 | Notify users that the page has been updated based on certain actions | Implementation | closed |  | 14.5.0 |  |
| MEET-65 | Document the new component and use it to replace streamable_flash_banner | Implementation | closed |  | 14.6.0 |  |
| MEET-86 | Keep scroll position when reloading a meeting through the update flash | Feature | closed |  | 14.6.0 |  |
| OP-15850 | Remove meeting update flash feature flag | Implementation | closed |  | 14.6.0 |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| OP-15890 | Bug | Reload banner gets triggered when a new item is added to a meeting | closed |  | 14.6.0 |  |  |
| DREAM-148 | Bug | Meeting reload banner is too narrow | closed |  | 14.6.0 |  |  |

## Technical Details

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

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Build Number |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Mir Bhatia |
| Product manager |  |
| Feature Lead |  |
| Developers | Mir Bhatia, Oliver Günther |
| Designer | Parimal Satyal |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a meeting facilitator, present or participant  
**I want to** know when someone has edited the meeting agenda concurrently  
**so that** I can have the latest version of the meeting agenda

##### **Acceptance criteria**

  - When a user on a Meeting agenda page and another user edits the same page concurrently,
    
      - Notify the user via a Primer banner (previously flash) that the page has been updated with a button to reload the page
    
      - The info banner/flash will be horizontally centered, with a "Reload" action.

  - ~~Update the banner in Notification center with this one.~~ (Might not be possible, the page is Angular-based).

#### Actions that trigger the flash

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p"><strong>Action</strong></p></td><td class="op-uc-table--cell"><p class="op-uc-p"><strong>Trigger flash?</strong></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Edit title</p></td><td class="op-uc-table--cell"><p class="op-uc-p">✅</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Edit details (time, location, duration...)</p></td><td class="op-uc-table--cell"><p class="op-uc-p">✅</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Edit participants (add or remove participants)</p></td><td class="op-uc-table--cell"><p class="op-uc-p">✖</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Edit attachments (add or remove attachments)<br><i>The flash will trigger once agenda items have been edited with the attachments</i></p></td><td class="op-uc-table--cell"><p class="op-uc-p">✖</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Editing agenda items (add new ones, remove, edit description)</p></td><td class="op-uc-table--cell"><p class="op-uc-p">✅</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Editing sections (add sections, remove sections)</p></td><td class="op-uc-table--cell"><p class="op-uc-p">✅</p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Reordering items</p></td><td class="op-uc-table--cell"><p class="op-uc-p">✅</p></td></tr></tbody></table></figure>

##### **A note on Primer components**

This Primer [banner](https://primer.style/components/banner) (previously [flash](https://primer.style/components/flash/)) offers a full and a *floating* version. As discussed with <mention class="mention" data-id="72512" data-type="user" data-text="@Marc Alcobé">@Marc Alcobé</mention> and <mention class="mention" data-id="39106" data-type="user" data-text="@Henriette Darge">@Henriette Darge</mention>, we'll use the smaller, non-full version for this. This is in contrast to the full version we use at the end of the file storage configuration flow. The difference is logical, since one is an expected success banner announcing the end of a multi-stage process and this one is an info banner announcing a punctual, unexpected but relevant information (that is often immediately dismissed, either with a close or a reload).

We'll also need to modify the behaviour of the Primer component to allow it to float with a fixed positioning on top of the viewport, such that it remains fixed even when scrolling the page.

##### Visuals

<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/105648/content">

##### **Mockup**

Figma link: <https://www.figma.com/file/cJDhzOmYMstUNRS3EmgqZ0/Meetings-Module?type=design&node-id=1995-28098&mode=design>

##### **Out of scope**

The current feature is a smaller fix to improve the usability of the Meetings module:

  - It does not offer in-place warnings for detection of concurrent, conflicting edits at an agenda-item, just a general one for the page.
    
      - This is similar to what we currently have in Notification centre.

  - Real-time editing would be an improvement over this but is a much larger feature, so these are out of scope:
    
      - Collaborative, real-time editing of agenda items: <mention class="mention" data-id="53776" data-type="work_package" data-text="###53776">###53776</mention>
    
      - Real-time editing in long text fields in general: <mention class="mention" data-id="28933" data-type="work_package" data-text="###28933">###28933</mention>

  - No update notification outside of the page is offered. I.e. the notification bell and the in app notification center do not receive a message.
