# Epic OP-8687 - Dynamic meetings and agenda items linked to work packages

Project: OpenProject
Status: closed
URL: https://community.openproject.org/work_packages/OP-8687

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Votes | 2 |
| List |  |
| Target versions | 13.1.0 |
| Sprint | 13.1.0 |
| Backlog bucket |  |
| Relevance |  |

## Subitems

| ID | Type | Subject | Status | Assignee | Target versions | Project | Priority | Spent time |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| OP-12992 | Feature | Meeting module: Modes and permission levels | closed |  | 13.1.0 | OpenProject | Medium |  |
| OP-13227 | Implementation | Primer `Autocomplete` alternative needed | closed | Oliver Günther | 13.1.0 | OpenProject | Medium |  |
| OP-13228 | Implementation | Primer compatible CKEditor needed | closed | Oliver Günther | 13.1.0 | OpenProject | Medium |  |
| OP-13258 | Feature | Meetings tab on work package page  | closed |  | 13.1.0 | OpenProject | Medium |  |
| OP-13312 | Implementation | Primerized Rails-rendered autocomplete select needed | closed | Oliver Günther | 13.1.0 | OpenProject | Medium |  |
| OP-13329 | Implementation | Deal with cancelling and data loss | closed |  | 13.1.0 | OpenProject | Medium |  |
| OP-13334 | Feature | Activate meeting module and one meeting "weekly" to the seed data | closed |  | 13.1.0 | OpenProject | Medium |  |
| OP-13346 | Implementation | Add "Download ICS" functionality | closed |  | 13.1.0 | OpenProject | Medium |  |
| OP-13362 | Implementation | Meeting duration exceeded by agenda items warnings | closed |  | 13.1.0 | OpenProject | Medium |  |
| OP-13406 | Implementation | Journalize the MeetingAgendaItem class | closed |  | 13.1.0 | OpenProject | Medium |  |
| OP-13458 | Implementation | Cleaning up author information on user deletion | closed |  | 13.1.0 | OpenProject | Medium |  |
| OP-13469 | Implementation | Enable email notifications for structured meetings | closed |  | 13.1.0 | OpenProject | Medium |  |
| OP-13525 | Implementation | Update the Meeting acts_as_searchable declaration to include MeetingAgendaItems | closed |  | 13.1.0 | OpenProject | Medium |  |
| OP-13657 | Implementation | Remove n+1 queries | closed |  | 13.1.0 | OpenProject | Medium |  |
| OP-13714 | Feature | Show work package's meeting tab count | closed |  | 13.1.0 | OpenProject | Medium |  |
| OP-13716 | Feature | Mobile, the participant section should move to details section | closed |  | 13.1.0 | OpenProject | Medium |  |
| OP-13734 | Implementation | Add optimistic locking to meeting agenda items | closed |  | 13.1.0 | OpenProject | Medium |  |
| OP-13475 | Implementation | Keep MeetingAgenda items when deleting related Work Package | closed |  |  | OpenProject | Medium |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Module |
| --- | --- | --- | --- | --- | --- | --- |
| OP-13859 | Bug | Search not working on some meetings (possibly because of agenda items containing macros) | closed |  | 13.1.0 |  |
| OP-13644 | Documentation | Create documentation for meetings module 13.1 | closed | Maya Berdygylyjova | 13.1.0 |  |
| OP-13456 | Bug | Error 500 on Edit meeting title | closed |  | 13.1.0 |  |
| OP-13443 | Bug | Error 500 on Meeting details modal when Date is left empty | closed |  | 13.1.0 |  |
| OP-13810 | Bug | Meetings: editing notes on a work package agenda item is not possible | closed |  | 13.1.0 |  |
| OP-13793 | Bug | Meetings: missing "." in Created by line in header | closed |  | 13.1.0 |  |
| OP-13730 | Bug | Macros do not work in the new meetings | closed |  | 13.1.0 |  |
| OP-13630 | Bug | Error on the work package meetings tab not clear enough for users without Manage agendas permission | closed |  | 13.1.0 |  |
| OP-13625 | Bug | When autofill suggestion is used for the agenda title, the whole agenda item disappears | closed |  | 13.1.0 |  |
| OP-13621 | Bug | Meetings: adding work package item without selecting a work package results in an error | closed |  | 13.1.0 |  |
| OP-13606 | Bug | (Mobile) Date picker (calendar) opens automatically on iOS when Meeting details modal is opened | closed |  | 13.1.0 |  |
| OP-13578 | Bug | The new agenda item button has incorrect position | closed |  | 13.1.0 |  |
| OP-13474 | Bug | (Mobile) New meeting form's problematic layout | closed |  | 13.1.0 |  |
| OP-13470 | Bug | (Mobile) Page cannot be scrolled after Meeting details are edited | closed |  | 13.1.0 |  |
| OP-13468 | Bug | (Mobile) Author and duration overlap | closed |  | 13.1.0 |  |
| OP-13466 | Bug | No spacing between "Undisclosed work package" and duration | closed |  | 13.1.0 |  |
| OP-13459 | Bug | Time zone displayed as GMT+00:00 after adding agenda item | closed |  | 13.1.0 |  |
| OP-13457 | Bug | Missing (broken) translation when total duration is exceeded | closed |  | 13.1.0 |  |
| OP-13282 | Documentation | Clarify naming and translations | closed |  | 13.1.0 |  |
| OP-13226 | Bug | Primer `Action Menu` overlay positioning issue | closed |  | 13.1.0 |  |
| OP-13253 | Code maintenance | Rework existing meetings into meeting agendas | rejected |  | 13.1.0 |  |
| OP-13607 | Bug | "Edit meeting details" tooltip visible when meeting details modal is cancelled | closed |  | 13.1.0 |  |
| OP-13472 | Bug | (Mobile) Date and time in Meeting details are not left aligned | closed |  | 13.1.0 |  |
| OP-13827 | Bug | Notes on Add work package to meeting modal are overflowing | closed |  | 13.1.1 |  |
| OP-13628 | Bug | Numbered list on Agenda notes difference between edit and saved state | closed |  |  |  |
| OP-13665 | Bug | Stimulus calls any keyboard event listener when Chrome autocomplete is triggered | on hold |  |  | Modules and project features / Meetings |
| OP-13627 | Bug | + sign not centered with time zone (Meeting details) on Firefox | on hold |  |  | Modules and project features / Meetings |

## Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Meetings |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Attila Dombi |
| Product manager |  |
| Feature Lead |  |
| Designer | Parimal Satyal |
| Developers | Attila Dombi |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

**As** a project member  
**I want to** build meeting agendas, add invitees and document important information and decisions  
**so that** our meetings are more efficient and key information is documented and easy to find.

### Acceptance criteria

A new Meetings module (based on Primer) will replace the existing one:

  - **A meeting consists of meeting details, agenda items and participants.**
  - **Meeting details are:**
      - Title of the meeting (required)
      - Date (required)
      - Time (required)
      - Duration (required)
          - If the set duration is longer than the sum of the duration of agenda items, the excess time is indicated with a "+ {minutes}"
          - Duration is used to derive meeting finish time
      - Location (optional)
  - The actions available to meeting participants depends on the permissions in relation to the Meetings module *(as set in Administration → Users and permissions → Roles and permissions)*  
    <mention class="mention" data-id="49334" data-type="work_package" data-text="###49334">###49334</mention>
  - A meeting can of one of two statuses:
      - **Open** 
          - All actions possible (based on available permissions)
      - **Closed**
          - Meeting becomes read-only except for users with "Close/re-open agenda items" and "Edit meetings" permissions
          - The "Edit meeting title", "Edit meeting details" and "Add participants" actions are no longer available
  - There is a "More" icon on the right edge of the title, with these options:
      - **Edit meeting title**
          - The title becomes an inline edit
      - **Download iCalendar event**
          - A static iCalendar file is available with meeting details (name, start/end time, location, organiser and a link to the meeting)
      - **Send email to all participants**
          - Sends an email with meeting details all participants (invitees and attendees)
          - *\[open\] Perhaps we should rename this to: "Send email reminder to participants"?*
      - **Delete meeting** (in red)
          - A browser confirmation is required before deletion
  - **Participants** are selected (as they were in the old Meetings module) in the create form

### Meetings index page

The current meetings index page in a project will be updated to accommodate the new Meetings module alongside the existing one.

  - The newer Primer-based meetings will be referred to as "Dynamic" meetings. Meetings created in the old style will be referred to as "Classic" meetings
  - A new "Type" column will be added to the index to indicate if a meeting is:
      - Dynamic or
      - Classic
  - The Create meeting form will offer the user a choice between a dynamic (default) or classic meeting.

### Right pane

  - The right pane (on desktop) consists of:
      - **Meeting details**
          - Title ("Meeting details")
          - Date 
          - Time 
          - Duration (if it exists)
          - Link (if it exists)
      - **Status**
          - Open (in green), with the text:
              - "This meeting is open. You can add/remove agenda items and edit them as you please. After the meeting is over, close it to lock it."
          - Closed (in grey), with the text:
              - "This meeting is closed. You cannot add/remove agenda items anymore."
          - A "Close meeting" or "Re-open meeting" action depending on the state
      - **Participants**
          - Title ("Participants") with a counter next to it with the total amount of invitees and attendees (one person counts once)
          - A list of the first 5 participants in alphabetical order
          - If there are more than 5 participants, a "Show {n} more" link
              - Clicking this will expand the list to show all participants
          - An "Add participants" action
              - This shows the existing participants feature (listing all project members, with two column of checkboxes for *Invited* and *Attended*) in a Primer modal
              - *Note: We are using an existing/old implementation that's not particularly in keeping with the overall modern, Hotwire-based design of the rest of the modal due to technical reasons.*

### Agenda items

  - Meetings consist of agenda items, which consist of:
      - **Title** (required)
      - **User** who added the agenda item (non-editable)
      - **Duration** (optional field)
          - Integer field, in minutes
          - *Risk: if some agenda items have duration and others don't; the total duration will be misleading since some items will have a duration of zero*
          - The information is hidden if no duration is input
          - This is in red if the duration of *this* item goes beyond the set meeting duration
      - Description (text area: CKEditor).
  - **The meeting title can also be replaced with a work package:**
      - The "Add" action gives users a choice between:
          - Agenda item
          - Work package
      - If a work package is selected:
          - The title input field becomes an autocomplete keyword search field, and typing keywords displays results in an overlay
          - The user can select the corresponding work package.
          - The title is now replaced with the work package details (id, subject, type, status)
          - Clicking on the work package title opens it in a new tab.
          - Functionally, other agenda elements (duration, notes) are unrelated to the work package and do not affect it.
  - **Every agenda item as a "more actions" menu** (behind the three-dot *more* button to the right of the user name) with these options:
      - Edit
      - Add notes
      - Move to top *(unless already on top)*
      - Move up *(unless already on top)*
      - Move down *(unless already in the bottom)*
      - Move to bottom *(unless already in the bottom)*
      - Delete *(in red)*

**Agenda items have two states, display and edit:**

  - *In display state*, agenda details cannot be edited but users with the necessarily edit permissions maybe drag them up and down to change the order.
  - *In edit state*, these fields are visible:
      - Title (text field, typing \# turns it into a search field)
      - Duration in minutes (integer)
      - "+ Notes"
          - Clicking this makes a CKEditor text area visible with label "Notes"
      - Cancel button (secondary)
      - Save button (primary)

### **Mobile**

  - The module has to be responsive. Viewing meetings is a priority on mobile.
  - I**n mobile mode, the module is single column.**
  - The contents of the right side pane (meeting details, status, participants) go on top above the agenda items
      - **Meeting status** is reduced to just one line:
          - The status (Open/Closed) on the left edge
          - The "Close/Re-open meeting" action on the right edge
      - **The participants section** is removed and replaced with an item in the Meeting details section, with a "Show all" action
          - {n} Participants [Show all](https://community.openproject.org/#)
          - Clicking on the action will show the regular participants modal
  - **Agenda item details** (title, user, duration) become multi-line:
      - Regular items: 
          - Line 1: Title
          - Line 2: User on the left edge, duration on the right edge
      - Work package items:
          - Line 1: Work package name
          - Line 2: {Type} {id} {status}
          - Line 2: User on the left edge, duration on the right edge

### **Export/integrations**

  - iCal download (not sync, download .ics file)
  - Print (browser)
      - \[open\] How does Primer deal with this?

### **Journalising:**

  - Modifications to a meeting are journalised (can be in the background, not visible to the user)
  - ~~There is a link to view meeting journal history~~

### **Email notifications:**

  - Send email notifications
      - When someone is invited (include .ics as attachment)
      - When meeting dates change (include .ics as attachment)
      - ~~When meeting status changes~~
      - When meeting is sent to invitees manually (include .ics as attachment)
  - Offer an "Email all participants" action
      - Sends meeting agenda to all invitees via email

### Open

  - How should we handle migration and old meetings?
      - \[Decision:\] Old meetings will be preserved as is and will live alongside the newer Primer meetings.

### Out of scope

This first version of the new Meetings module for version 13.1 will not include:

  - Duration derived from the duration of agenda items
  - Open points
      - <mention class="mention" data-id="49578" data-type="work_package" data-text="###49578">###49578</mention>
  - Commenting and emoji reactions and comment threads
  - Sections
  - Create work packages directly from an agenda item
  - Agenda backlog (a set of agenda items that are "parked" and do not show up in the actual meeting, simliar to drafts)
  - Open linked work package in a split scree\_n.\_
  - Move existing agenda item to another meeting
  - Meeting series (recurring)
  - In-app notifications:
  - iCal sync
  - Decision and issues log
  - Meeting modes and statuses
      - <mention class="mention" data-id="49334" data-type="work_package" data-text="###49334">###49334</mention>

Some of these will be addressed in a later iteration and will be described in this epic:

<mention class="mention" data-id="50689" data-type="work_package" data-text="###50689">###50689</mention>

### Mockup

**Figma link:**  
<https://www.figma.com/file/cJDhzOmYMstUNRS3EmgqZ0/Meeting-Module-co-creation?type=design&amp;node-id=0-1&amp;mode=design>

# User Problem

## User

  - Project manager
  - Project member
  - Meeting moderator
  - Meeting member

## Problem

  - Tasks and issues are tracking in the work packages module.
  - Meeting agendas and meeting minutes are tracked in the meetings module.
  - In project meetings very often open issues are discussed.

## Pain

  - The information needs to be tracked in two modules. This leads to extra work and outdated information.

# Business Case

## Solution

  - It is possible to create relations between meeting agendas/meeting minutes and work packages/work package comments.
  - This link is visible and and editable in both modules.
  - It is possible to change work package comments. Changes in comments are journalized.
  - Meeting agenda preparation
      - It is possible to order topics in the meeting agendas/minutes by drag and drop.
      - Topics have an allocated time.
      - Based on the start date of the meeting, the allocated time and the order of the meeting items the expected start is derived.
  - Meeting agendas and meeting minutes that include work package content are "freezed". This means that changes in work packages do not change the meeting minutes.

## Out of Scope for the MVC

  - Printing (usual browser print)
  - Calendar integration (iCalendar).
  - Showing meetings in the Gantt chart/calendar.
  - Recurring meetings.

## Differentiation

  - There is no other tool that connects operations issue tracking with tool based meeting management.

## Next iteration

  - "Auf Wiedervorlage".
  - Integrationen mit Kalender-Applikationen

# Launch and Growth

## Measures

  - Created meetings per user and projects.

## Messaging

<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Headline</p></th><td class="op-uc-table--cell"><p class="op-uc-p">Create meeting agendas and meeting minutes based on work package comments.</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">First Paragraph</p></th><td class="op-uc-table--cell"><p class="op-uc-p">You can now add a work package to a meeting agenda by adding a comment to the work package. So all information to make a decision is accessible in one place. So there is no need to add information in two different places.&nbsp;</p></td></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Customer Quote</p></th><td class="op-uc-table--cell"><p class="op-uc-p">In the past I had to manually create a meeting agenda. So I had to ask the project team to put their open issues on the agenda. After a meeting I had to also add the decision to those issues. With the integration I save a lot of time. And more importantly: It adds a lot of transpareny and control.</p></td></tr></tbody></table></figure>

## Go to market

*How are you planning on getting this into users' hands?*
