# Feature OP-13258 - Meetings tab on work package page 

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

## Planning

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

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| OP-13477 | Number of meetings in the tab header not displayed | Implementation | new |  | Wish List |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| OP-13485 | Bug | Not visible meetings are shown in the meeting tab | closed |  | 13.1.0 |  |  |

## Technical Details

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

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| 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 specified in parts here <mention class="mention" data-id="37297" data-type="work_package" data-text="#37297">\#37297</mention>, a pain of using the existing meeting module lies in tracking data in two modules: decisions discussed and noted in a meeting around a specific work package using the meeting module need to be somehow manually duplicated in the work package page. A main idea of the new meeting module was, to resolve this issue. Results of a meeting should be automatically available within the work package page, increasing transparency and the history of discussions around a work package without manual effort.

Formulated as a "user stories", it might sound like this:

"As a user working on work packages, I want to have an easily accessible overview within the work package page of what was discussed in meetings around a specific work package without digging through meetings manually."

"As a meeting moderator, I don't want to manually duplicate notes/minutes from a meeting to all related work package pages. Instead, the notes/minutes should be a available automatically on a work package page."

The current development state of the implementation of <mention class="mention" data-id="49413" data-type="work_package" data-text="#49413">\#49413</mention> already offers a relation between an `AgendaItem` and a `WorkPackage` (`WorkPackage` has many `AgendaItems`, `AgendaItem` belongs to `WorkPackage`). It's already possible to set this relation up when creating a new `AgendaItem` within the meeting UI. Such an `AgendaItem` optionally contains `notes` as a text field.

Technically it would be relatively easy to use this relation to render a (read-only\!) list of all `AgendaItems` of a `WorkPackage` in a chronological ordered list within a tab (called "Meetings"?) on a `WorkPackage` page. Optionally (at least part of) the notes of each `AgendaItem` could be rendered as well. Additionally the information and link to the parent `Meeting` of each `AgendaItem` can be displayed in this list as well.

The "meeting" tab is shown, when the meeting module is activated for the project. Whoever has access to the meeting module in this project would also see all `AgendItems` and their notes in the new tab on `WorkPackage` page.

**Update 1**: Adding a `WorkPackage` to a `Meeting` (through an `AgendaItem`) should be possible from within the "meetings" tab on the `WorkPackage` page.

**Update 2**: Displaying `AgendaItems` of upcoming `Meetings` in this this tab would make sense as well

**Acceptance criteria**

  - A meeting tab is added to a work package 
      - The meeting tab is currently visible if the user is able to see view meetings in the work package's project
      - \[open\] The work package might be added to other project's meetings, or the user might be able to view part of the meetings
  - The meeting tab shows meetings that
      - the work package has been added to
      - the user is able to see the respective meeting
  - The meeting tab allows to add the work package to a meeting (currently requires edit\_meeting permissions, but bound to change to create\_meeting\_agendas)
      - A dialog opens where the user can select all visible upcoming meetings that have the state "open"
      - An optional note can be added to the meeting agenda item
      - When saved, an agenda item with the work package being linked is added to the bottom of the meeting. The executing user is made the author of that agenda item
  - The meeting tab allows to filter for upcoming and past meetings using a tabbed display. All *visible* meetings the work package has been added to are listed there.