Content
View differences
Updated by Jens Ulferts 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.
* **\[open\]** After clicking on the create button, how will the user select the project the new item (Boards, Meetings, Team planner) is to be created in? Will the selection become part of the creation form for Meetings? For Boards and Team planners, no form exist, though. When creating an item, will the application switch into the project context selected (see before) by the user or will it stay in the global context?
* 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.
* **\[open\]** What is the default sort criteria of the items?
* **\[open\]** Two technologies are used for the project scoped pages as of now: Angular for Boards and Team planner and Rails for Meetings. For Angular (Boards and Team planner), we could apply the work package based approach easily. For Rails (Meetings), the using a dropdown with two options would require more work. The easiest would be to apply the same pattern we use for the projects table where clicking once will switch between sorting by that column ascending and descending.
* **\[open\]** There might be hundreds or thousands of items on the global index pages. Is pagination applied here in the normal fashion?
* 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
* A separate work package will be created (##48014) to add all this modules also to the "+" button in the navigation bar.
## 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.
## 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.
* **\[open\]** After clicking on the create button, how will the user select the project the new item (Boards, Meetings, Team planner) is to be created in? Will the selection become part of the creation form for Meetings? For Boards and Team planners, no form exist, though. When creating an item, will the application switch into the project context selected (see before) by the user or will it stay in the global context?
* 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.
* **\[open\]** What is the default sort criteria of the items?
* **\[open\]** Two technologies are used for the project scoped pages as of now: Angular for Boards and Team planner and Rails for Meetings. For Angular (Boards and Team planner), we could apply the work package based approach easily. For Rails (Meetings), the using a dropdown with two options would require more work. The easiest would be to apply the same pattern we use for the projects table where clicking once will switch between sorting by that column ascending and descending.
* **\[open\]** There might be hundreds or thousands of items on the global index pages. Is pagination applied here in the normal fashion?
* 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
* A separate work package will be created (##48014) to add all this modules also to the "+" button in the navigation bar.
## 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.
## 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