Content
View differences
Updated by Marc Alcobé 9 months ago
**As** a portfolio manager or board member
**I want to** access the overview and critical information for my companies workspaces in a clear navigation
**so that** I can check this information on the go easily
## **Acceptance criteria**
#### **Global**
* [ ] The currently called `Portfolio management` module is renamed to `Workspaces`.
* [ ] The icon of the module is no longer the `briefcase` one but the `project` one.
#### **Workspaces index**
* [ ] When the user enters this module with all see permissions and there are both portfolios and programs they find:
* [ ] Three fixed entries at the top of the screen for: Portfolios, Programs and Favourites.
* [ ] A collapsable sub-header for `All workspaces` that expands and collapses all the entry points below, including:
* [ ] Search bar and segmented control with All and Favourites.
* [ ] The list of all the visible portfolios, programs, and projects in a hierarchy list. The hierarchy list should be expandable and collapsable on the higher levels of hierarchy. Each entry point will have the following information:
* [ ] Icon indicating if it is a portfolio, program, or project.
* [ ] Name of the workspace.
* [ ] Star icon if the workspace has been marked as favourite.
* [ ] A chevron (if it has sub-elements) to expand or collapse the levels below the point. Note that only the chevron should expand and collapse, clicking anywhere else in the list element should open the overview page of that workspace.
* [ ] A new approach to truncating the workspaces names, inspired by the solution used by iOS, is to be implemented. When the name needs to be truncated, we will keep the last 15 characters of the name and then truncate in between with `…`.
* [ ] When the user uses the segmented control for favourites or search by name functionalities, the results should be displayed normally, but its parent items in the hierarchy should also be displayed but greyed out.
* [ ] By default, the all workspaces section elements are all collapsed, collapsed besides the two first higher levels of the hierarchy. levels.
#### **Portfolios, Programs, and Favourites indexes**
* [ ] The portfolio and programs index page has:
* [ ] Search bar.
* [ ] Segmented control for All and Favourites.
* [ ] All the portfolios or programs will be displayed in a border box but with some extra information:
* [ ] Icon + Name + Star icon (if marked as favourite).
* [ ] Description.
* [ ] Status.
* [ ] Amount of sub-elements: sub-portfolios, programs and projects.
* [ ] The favourites index page has:
* [ ] Search bar.
* [ ] All the hierarchy that includes the workspaces marked as favourite.
## **Technical notes**
* ##
## **Permissions and visibility considerations**
* Need to read which permissions do the user have to see Portfolios, and Programs.
* If the user can't see these entities, hide the entry points for them.
## **Visual reference**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:320px;" src="/api/v3/attachments/774365/content">
## **Out of scope**
* Connect the new API module created in the web app: <mention class="mention" data-id="66254" data-type="work_package" data-text="###66254">###66254</mention>
**I want to** access the overview and critical information for my companies workspaces in a clear navigation
**so that** I can check this information on the go easily
## **Acceptance criteria**
#### **Global**
* [ ] The currently called `Portfolio management` module is renamed to `Workspaces`.
* [ ] The icon of the module is no longer the `briefcase` one but the `project` one.
#### **Workspaces index**
* [ ] When the user enters this module with all see permissions and there are both portfolios and programs they find:
* [ ] Three fixed entries at the top of the screen for: Portfolios, Programs and Favourites.
* [ ] A collapsable sub-header for `All workspaces` that expands and collapses all the entry points below, including:
* [ ] Search bar and segmented control with All and Favourites.
* [ ] The list of all the visible portfolios, programs, and projects in a hierarchy list. The hierarchy list should be expandable and collapsable on the higher levels of hierarchy. Each entry point will have the following information:
* [ ] Icon indicating if it is a portfolio, program, or project.
* [ ] Name of the workspace.
* [ ] Star icon if the workspace has been marked as favourite.
* [ ] A chevron (if it has sub-elements) to expand or collapse the levels below the point. Note that only the chevron should expand and collapse, clicking anywhere else in the list element should open the overview page of that workspace.
* [ ] A new approach to truncating the workspaces names, inspired by the solution used by iOS, is to be implemented. When the name needs to be truncated, we will keep the last 15 characters of the name and then truncate in between with `…`.
* [ ] When the user uses the segmented control for favourites or search by name functionalities, the results should be displayed normally, but its parent items in the hierarchy should also be displayed but greyed out.
* [ ] By default, the all workspaces section elements are all collapsed,
#### **Portfolios, Programs, and Favourites indexes**
* [ ] The portfolio and programs index page has:
* [ ] Search bar.
* [ ] Segmented control for All and Favourites.
* [ ] All the portfolios or programs will be displayed in a border box but with some extra information:
* [ ] Icon + Name + Star icon (if marked as favourite).
* [ ] Description.
* [ ] Status.
* [ ] Amount of sub-elements: sub-portfolios, programs and projects.
* [ ] The favourites index page has:
* [ ] Search bar.
* [ ] All the hierarchy that includes the workspaces marked as favourite.
## **Technical notes**
* ##
## **Permissions and visibility considerations**
* Need to read which permissions do the user have to see Portfolios, and Programs.
* If the user can't see these entities, hide the entry points for them.
## **Visual reference**
<img class="image_resized op-uc-image op-uc-image_inline" style="width:320px;" src="/api/v3/attachments/774365/content">
## **Out of scope**
* Connect the new API module created in the web app: <mention class="mention" data-id="66254" data-type="work_package" data-text="###66254">###66254</mention>