Content
View differences
Updated by Henriette Darge 28 days ago
**Acceptance criteria**
* The global project selector can expand/collapse list has a split layout
* Left: TreeView with the project hierarchy nodes
* Per defaullt, all nodes are collapsed
Collapsed per default
* Clicking on the name of a project, leads you to that project
* Open: Should the treeview respect the currently active filters?
* Right: The unchanged project table
**Technical notes**
* The limit for the project selector remains Use Primer::Alpha::Layout
* The Primer::OpenProject::FilterableTreeView Use the same logic and style we have for example for CF of type hierarchy
**Permissions and visibility considerations**
* _Only projects visible to the user should be extended for this to support async loading and filtering shown_
**Out of scope**
* Remembering what was collapsed and what was expanded after page reload Changing the left side menu
* The global project selector can expand/collapse
* Left: TreeView with the project
* Clicking on the name of a project, leads you to that project
* Open: Should the treeview respect the currently active filters?
* Right: The unchanged project table
* The limit for the project selector remains
* The Primer::OpenProject::FilterableTreeView
**Permissions and visibility considerations**
* _Only projects visible to the user
**Out of scope**
* Remembering what was collapsed and what was expanded after page reload