Content
View differences
Updated by Marc Alcobé about 3 years ago
# User Problem
## User
_What persona, persona segment, or customer type experiences the problem most acutely?_
* All users
## Problem
_What problem or job does the user have?_
* 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
_What is the primary workaround that users perform that we could remove or replace? Why is it painful?_
* 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 each module.
* Existing ones:
* Projects
* Work packages
* News
* Time and costs
* New ones:
* Meetings
* Boards
* Team planners
## Acceptance criteria
* Add a new entry for all the new index pages created (**Boards**, **Meetings** and **Team planners**) in the dropdown menu from the grid menu icon in the navigation bar. Now this menu entries will also have icons.
* Create an index page without sidebar for **Boards** with a table containing this columns:
* Name (names will be links)
* Project
* Type
* Created on
* Create an index page without sidebar for **Meetings** with a table containing this columns:
* Name (names will be links)
* Project
* Start date
* Duration
* Location
* Create an index page without sidebar for **Team planners** with a table containing this columns:
* Name (names will be links)
* Project
* Created on
* All index pages will have a button to create **Boards**, **Meetings** or **Team planners** in the top right corner of the screen.
* The forms to create boards, meetings and team planner have a mandatory form field to select the project. The newly created a new board, meeting or team planner is then opened inside of the selected project. For **Boards** the addition of project selection is done in ##47989.
* All the columns in this tables should be sortable using the same method of sorting through the header of the columns as in the work packages tables.
* Default sort behaviour:
* Meetings: Sorted by date
* Boards: Sort alphanumerically by name (ascending)
* Team Planner: Sort alphanumerically by name (ascending)
* Same UX 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: Similar 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 (table view).
## Notes
* There is a separate work package (##48014) to add all this modules also to the "+" button in the navigation bar.
* There is a separate work package (##48142) to add the sidebar in the global navigation concept and indexes.
## Out of Scope for the MVP
* Add new components to the design system.
* Have a system to add favourites in the index pages.
* Have a sidebar menu navigation for every module.
* Calendars index page.
# Implementation plan
* The global scope of this EPIC is divided in:
* Creation of the global index pages (##48160)
* Global boards creation flow (##47989)
* Global meetings creation flow (##48114)
* Global team planner creation flow (##48161)
* There is a separate work package (##48014) to add all this modules also to the Advanced "+" button in the navigation bar.
* There is a separate work package (##48142) to add the sidebar in the global navigation concept and indexes. Calendars index page.
# ## Visuals
#### Global indexes:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/55866/content">
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/55867/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/55868/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/55869/content">
#### Meetings inside a project:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/55870/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/55871/content">
## 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
_What persona, persona segment, or customer type experiences the problem most acutely?_
* All users
## Problem
_What problem or job does the user have?_
* 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
_What is the primary workaround that users perform that we could remove or replace? Why is it painful?_
* 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 each module.
* Existing ones:
* Projects
* Work packages
* News
* Time and costs
* New ones:
* Meetings
* Boards
* Team planners
## Acceptance criteria
* Add a new entry for all the new index pages created (**Boards**, **Meetings** and **Team planners**) in the dropdown menu from the grid menu icon in the navigation bar. Now this menu entries will also have icons.
* Create an index page without sidebar for **Boards** with a table containing this columns:
* Name (names will be links)
* Project
* Type
* Created on
* Create an index page without sidebar for **Meetings** with a table containing this columns:
* Name (names will be links)
* Project
* Start date
* Duration
* Location
* Create an index page without sidebar for **Team planners** with a table containing this columns:
* Name (names will be links)
* Project
* Created on
* All index pages will have a button to create **Boards**, **Meetings** or **Team planners** in the top right corner of the screen.
* The forms to create boards, meetings and team planner have a mandatory form field to select the project. The newly created a new board, meeting or team planner is then opened inside of the selected project. For **Boards** the addition of project selection is done in ##47989.
* All the columns in this tables should be sortable using the same method of sorting through the header of the columns as in the work packages tables.
* Default sort behaviour:
* Meetings: Sorted by date
* Boards: Sort alphanumerically by name (ascending)
* Team Planner: Sort alphanumerically by name (ascending)
* Same UX 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: Similar 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 (table view).
##
* There is a separate work package (##48014) to add all this modules also to the "+" button in the navigation bar.
* There is a separate work package (##48142) to add the sidebar in the global navigation concept and indexes.
##
* Add new components to the design system.
* Have a system to add favourites in the index pages.
* Have a sidebar menu navigation for every module.
* Calendars index page.
# Implementation plan
* The global scope of this EPIC is divided in:
* Creation of the global index pages (##48160)
* Global boards creation flow (##47989)
* Global meetings creation flow (##48114)
* Global team planner creation flow (##48161)
* There is a separate work package (##48014) to add all this modules also to the
* There is a separate work package (##48142) to add the sidebar in the global navigation concept and indexes.
#
#### Global indexes:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/55866/content">
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/55867/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/55868/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/55869/content">
#### Meetings inside a project:
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/55870/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/55871/content">
## 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