Content
View differences
Updated by Parimal Satyal over 1 year ago
**As** a project member who is often invited to various meetings
**I want to** easily be able to navigate through relevant meetings (in the future and the past) in one place
**so that** I don't have to worry about missing information by not being in the right page
#### Context
Currently, the user has to manually change individual filter criteria or change pages to switch between past and upcoming meetings, and between invitations and all meetings. This feature process is part of cumbersome and especially complicated in a larger epic mobile view. The goal with this redesign is to modernise the Meetings module and make it possible to get to the most relevant meetings via do all this in one page ("All meetings"), so that she can find the relevant meeting(s) without having to faff around and change views. This is particularly useful on mobile. faffing around.
The improvements to the Quick filter system are a separate/parallel feature specified here: #FEATURE (to be created). #### **Acceptance criteria**
_**Note:** Some of the criteria make references to meeting series or recurring meetings (feature ##54750). They are marked with \* and can be ignored until recurring meetings are implemented._
### Acceptance criteria
The meeting index pages are Primerised such that:
* It uses the PageHeader with the name of the view as the title (eg. "My Meetings")
* The Limit sidebar items are reorganised in two sections: entries to:
* Default views (no heading):
* My All meetings
* Recurring meetings\*
* All meetings
(once implemented)
* **Meeting series:\***
* (list of Meeting series belonging to the project or the instance)
* **Involvement**
* Invitations
* Attended
* Created by me
* **My Meetings** is Make "All meetings" the default view
* The **\+ Meeting** primary action In each index page (we'll take the "All meetings" for the following example), the sub-header has two options: these actions:
* Dynamic meeting Segment control to switch between: "Upcoming" (default) and "Past"
* Classic meeting
A drop-down to switch between: "Invitations" (default) and "Show all"
* The new quick filter system is described separately:
* #FEATURE (to be created) Add meeting (right-edge)
* The table is replaced Primerise the meeting list with a **Primer box design**
* The heading row has section/box design, with these "columns": columns:
* Title
* Project (if global) (when project not selected)
* Date and time
* Duration
* Location
* Each meeting is represented as a row, with a "More" icon at the end
* The More button displays a drop down with these options:
* Open this meeting
* View meeting series\*
* Delete
### Figma #### Visuals
[https://www.figma.com/design/cJDhzOmYMstUNRS3EmgqZ0/Meetings-Module?node-id=2124-14163](https://www.figma.com/design/cJDhzOmYMstUNRS3EmgqZ0/Meetings-Module?node-id=2124-14163) Pelase view [Figma mockups](https://www.figma.com/design/cJDhzOmYMstUNRS3EmgqZ0/Meetings-Module?node-id=2261-14165) for the most updated mockups.
**Desktop - upcoming invitations**
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/197822/content">
**Desktop - all upcoming**
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/197823/content">
**Mobile - upcoming invitations**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:380px;" src="/api/v3/attachments/197826/content">
**Mobile - all upcoming**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:380px;" src="/api/v3/attachments/197827/content">
**I want to** easily be able to navigate through relevant meetings (in the future and the past) in one place
**so that** I don't have to worry about missing information by not being in the right page
Currently, the user has to manually change individual filter criteria or change pages to switch between past and upcoming meetings, and between invitations and all meetings.
The improvements to the Quick filter system are a separate/parallel feature specified here: #FEATURE (to be created).
_**Note:** Some of the criteria make references to meeting series or recurring meetings (feature ##54750). They are marked with \* and can be ignored until recurring meetings are implemented._
### Acceptance criteria
The meeting index pages are Primerised such that:
* It uses the PageHeader with the name of the view as the title (eg. "My Meetings")
* The
* Default views (no heading):
* My
* All meetings
* (list of Meeting series belonging to the project or the instance)
* **Involvement**
* Invitations
* The **\+ Meeting** primary action
* Dynamic meeting
* Classic meeting
* #FEATURE (to be created)
* The table is replaced
* The heading row has
* Title
* Project (if global)
* Date and time
* Duration
* Location
* Each meeting is represented as a row, with a "More" icon at the end
* The More button displays a drop down with these options:
* Open this meeting
* View meeting series\*
* Delete
### Figma
[https://www.figma.com/design/cJDhzOmYMstUNRS3EmgqZ0/Meetings-Module?node-id=2124-14163](https://www.figma.com/design/cJDhzOmYMstUNRS3EmgqZ0/Meetings-Module?node-id=2124-14163)
**Desktop - upcoming invitations**
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/197822/content">
**Desktop - all upcoming**
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/197823/content">
**Mobile - upcoming invitations**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:380px;" src="/api/v3/attachments/197826/content">
**Mobile - all upcoming**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:380px;" src="/api/v3/attachments/197827/content">