Content
View differences
Updated by Marc Alcobé almost 3 years ago
# User Problem
## User
* All users
## Problem
* Currently all modules are linked to a project.
* Navigating to a module means to first select the project and then navigate to the module inside of the project.
## Pain
* It is hard to find and navigate to the respective module if the user does not know in what project the content is located.
* Users have long lists of bookmarks in their browser to get to the views they need.
# Solution
Building global index pages for all modules:
* Existing ones:
* Projects
* Work packages
* News
* Time and costs
* New ones:
* Meetings
* Boards
* Team planners
## Acceptance criteria
* Add a new entry for **Boards**, **Meetings,** **Meetings** and **Team planners** and **Calendars** in the dropdown menu with the grid menu icon in the navigation bar. Now this menu entries will also contain icons.
* Create an index page without sidebar for **Boards:**
* The index table will have this columns:
* Name (names will be links)
* Project
* Type
* Created on
* Sort alphanumerically by name (ascending)
* Create an index page without sidebar for **Meetings**:
* The index table will have this columns:
* Name (names will be links)
* Project
* Start date
* Duration
* Location
* Sorted by date with only upcoming meetings (including today) for the global index page, ordered by start date ascending until the implementation of #48142 is done.
* Create an index page without sidebar for **Team planners**:
* The index table will have this columns:
* Name (names will be links)
* Project
* Created on
* Sort alphanumerically by name (ascending)
* Create an index page without sidebar for **Calendars**:
* The index table will have this columns:
* Name (names will be links)
* Project
* Created on
* Sort alphanumerically by name (ascending)
* Same column sorting pattern like in the project table (not like in the work packages table): Clicking on a column header sorts ascending. Clicking the second time on the same column header sorts descending.
* Paginations should be the same pattern like implemented in other tables
* In the case of **Meetings** it is also necessary that the current "index" page inside of a project changes and adapts to the design for the global index. This one though will be sorted by start dated ascending. So there it might be possible, that when a lot of past meetings exist, we are not showing the most relevant to the user until the implementation of #48142 is done.
## Out of Scope
* The create buttons on this screens will be implemented separately into ##48160.
* Navigation sidebars will be implemented separately in ##48142.
* Add new components to the design system.
* Have a system to add favourites in the index pages.
* Calendars index page.
# Implementation plan
* Boards global index page (##48250)
* Meetings global index page (##48219)
* Team planner global index page (##48249)
# Visuals in Figma
* **Global indexes:** https://www.figma.com/file/v0V2OoFGVq1NQycQbm0FcC/Home-page-and-global-indexes?node-id=1%3A4&t=pODkm620Rz4sDC34-1
* **Meetings index in project:** https://www.figma.com/file/QlIXG2gWswucNsu6KAJCrI/Meetings?node-id=0-1
## User
* All users
## Problem
* Currently all modules are linked to a project.
* Navigating to a module means to first select the project and then navigate to the module inside of the project.
## Pain
* It is hard to find and navigate to the respective module if the user does not know in what project the content is located.
* Users have long lists of bookmarks in their browser to get to the views they need.
# Solution
Building global index pages for all modules:
* Existing ones:
* Projects
* Work packages
* News
* Time and costs
* New ones:
* Meetings
* Boards
* Team planners
## Acceptance criteria
* Add a new entry for **Boards**, **Meetings,**
* Create an index page without sidebar for **Boards:**
* The index table will have this columns:
* Name (names will be links)
* Project
* Type
* Created on
* Sort alphanumerically by name (ascending)
* Create an index page without sidebar for **Meetings**:
* The index table will have this columns:
* Name (names will be links)
* Project
* Start date
* Duration
* Location
* Sorted by date with only upcoming meetings (including today) for the global index page, ordered by start date ascending until the implementation of #48142 is done.
* Create an index page without sidebar for **Team planners**:
* The index table will have this columns:
* Name (names will be links)
* Project
* Created on
* Sort alphanumerically by name (ascending)
* Create an index page without sidebar for **Calendars**:
* The index table will have this columns:
* Name (names will be links)
* Project
* Created on
* Sort alphanumerically by name (ascending)
* Same column sorting pattern like in the project table (not like in the work packages table): Clicking on a column header sorts ascending. Clicking the second time on the same column header sorts descending.
* Paginations should be the same pattern like implemented in other tables
* In the case of **Meetings** it is also necessary that the current "index" page inside of a project changes and adapts to the design for the global index. This one though will be sorted by start dated ascending. So there it might be possible, that when a lot of past meetings exist, we are not showing the most relevant to the user until the implementation of #48142 is done.
## Out of Scope
* The create buttons on this screens will be implemented separately into ##48160.
* Navigation sidebars will be implemented separately in ##48142.
* Add new components to the design system.
* Have a system to add favourites in the index pages.
* Calendars index page.
# Implementation plan
* Boards global index page (##48250)
* Meetings global index page (##48219)
* Team planner global index page (##48249)
# Visuals in Figma
* **Global indexes:** https://www.figma.com/file/v0V2OoFGVq1NQycQbm0FcC/Home-page-and-global-indexes?node-id=1%3A4&t=pODkm620Rz4sDC34-1
* **Meetings index in project:** https://www.figma.com/file/QlIXG2gWswucNsu6KAJCrI/Meetings?node-id=0-1