Content
Updated by Marc Alcobé 17 days ago
**As** a user
**I want to** see different representations for "Program", "Portfolio" and "Project" in dropdowns and lists
**so that** I can easily distinguish between the three
## **Acceptance criteria**
#### **Type representations:**
* The new the different workspace types are differentiated by icons:
* Project: `project`
* Program: `versions`
* Portfolio: `briefcase`
#### **Workspaces list:**
* The `project list` module is renamed to `Workspaces`
* Its table will to will have a new column, `Type` where the workspace type with an icon and label will be displayed. icons are present in:
* The column should be filterable and sortable.
* The creation button to `+ Project` is now renamed `+ Add` and opens a dropdown with all three options of workspace creation with each icon represented.
#### Workspaces dropdown:
* The new project dropdown should open the hierarchy containing all the three types of workspaces.
* The new dropdown modal should take a bigger width of `640px`.
project list
* The name of the projects should be truncated at the end of the modal preserving always visible, if present, the favorite star and the type label. dropdowns for project selection (e.g. parent projects)
* The dropdown header is removed and the search bar and `All | Favorite` toggle switch are now in a single line.
* The star to indicate favorite workspaces is maintained.
* The icon and label to indicate Portfolios and Programs is added in the latest position after the name of the workspace and star (if present).
* The projects don't have icon or label indicator.
* The `+ Project` button in the project dropdown and (now used for all workspaces) should be removed together with the `Project lists` button in the footer should be removed.
* _\[open\] Why not using turbo directly to update this component without using the TreeView component? Loading times are too high?_
* _\[open\] If angular is kept, can we update the search bar and toggle switch to look like primer?_
#### Others:
* The dropdown for project selection, like parent projects… (excluding type project) should also contain the information of the workspace type as done in the workspaces' dropdown. button.
## **Figma**
* Workspaces lists: https://www.figma.com/design/bDgY4i9P5Bp2wAjNV0yeU0/Portfolios-module?node-id=194-7536
* Workspaces dropdown: https://www.figma.com/design/bDgY4i9P5Bp2wAjNV0yeU0/Portfolios-module?node-id=1-20105
## **Technical notes**
* _none_ <br>
## **Permissions and visibility considerations**
* _none_ none
## **Translation considerations**
* _none_
## **Out of scope**
* Replacing replacing the project dropdown (for navigation) by a filterable tree view.
* Same same is true for other project dropdown dropdowns&nbsp;
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** see different representations for "Program", "Portfolio" and "Project" in dropdowns and lists
**so that** I can easily distinguish between the three
## **Acceptance criteria**
#### **Type representations:**
* The new
* Project: `project`
* Program: `versions`
* Portfolio: `briefcase`
#### **Workspaces list:**
* Its table will to will have a new column, `Type` where the workspace type with an icon and label will be displayed.
* The column should be filterable and sortable.
* The
#### Workspaces dropdown:
* The dropdown header is removed and the search bar and `All | Favorite` toggle switch are now in a single line.
* The star to indicate favorite workspaces is maintained.
* The icon and label to indicate Portfolios and Programs is added in the latest position after the name of the workspace and star (if present).
* The projects don't have icon or label indicator.
* The `+ Project` button in the
* _\[open\] Why not using turbo directly to update this component without using the TreeView component? Loading times are too high?_
* _\[open\] If angular is kept, can we update the search bar and toggle switch to look like primer?_
#### Others:
* The dropdown for project selection, like parent projects… (excluding type project) should also contain the information of the workspace type as done in the workspaces' dropdown.
## **Figma**
* Workspaces lists: https://www.figma.com/design/bDgY4i9P5Bp2wAjNV0yeU0/Portfolios-module?node-id=194-7536
* Workspaces dropdown: https://www.figma.com/design/bDgY4i9P5Bp2wAjNV0yeU0/Portfolios-module?node-id=1-20105
## **Technical notes**
* _none_
## **Permissions and visibility considerations**
* _none_
## **Translation considerations**
* _none_
## **Out of scope**
* Replacing
* Same
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._