Content
View differences
Updated by Jens Ulferts 9 months ago
**As** a portfolio manager
**I want to** access portfolios easily in OpenProject
**so that** I can have a quick overview on what portfolio I need to work next
**Acceptance criteria**
* A new global module is created named `Portfolios`
* It has entry points in both global sidebar and grid icon for global menu
* The current `Project lists` module is renamed to `Workspaces`
* Inside the portfolios' module, there are four views/queries that are not editable:
* All portfolios
* My portfolios
* Favourite portfolios
* Archived portfolios
* The user cannot save personalised queries or views
* The view can be filtered, searched and sort (by the sort by button on the more icon). On top of that, users can create new portfolios.
* In each view, in the content, an index page to access portfolios will be created with a new border box component based in Primer. Each border box element will contain the following information:
* Portfolio name
* Portfolio status (_\[open\]_ should it be editable?)
* Portfolio description
* Progress bar with sub-items status
* Favourite indication (Transparent IconButton star)
* Amount of programs in the portfolio
* Amount of project in the portfolio
* Budget information including total budget and budget spent
* Last updated
* The progress bar with the status should have a hover card with the index details
* The sort by functionality is extracted from the current implementation of `Project lists`
* Creating a new portfolio opens the form for portfolio creation based on the project creation one.
**Technical notes**
* <br>
**Permissions and visibility considerations**
* For _\[open\]_ Do we have a user permission to see the Portfolio module they either have `see portfolios`?
* `create portfolios` (##66612)
* Any permission in an active portfolio.
* For Currently, seeing a user portfolio requires to see be member (with whatever permission) in a portfolio listed in portfolio. That is the Portfolio module (or in same as the Project module, or behaviour we have in the Project/Workspace dropdown, or anywhere else place for projects. There also isn't a specific permission to see projects (as far as users are concerend - there is one in the application) they need to have code), so not having a least one specific permission in that portfolio and the portfolio needs to see portfolios should be active. The behaviour is good enough.
* _\[open\]_ If a user can't `create portfolios`, should he see the same as for projects. `Portfolios` module?
* That might mean, that a member of a program or project cannot We would at least have to show the module whenever
* The user can see at least one portfolio
* Can create a portfolio of which the project is part because of lacking permissions. This is also the same behaviour currently in place for projects.
**Translation considerations**
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">EN</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">DE</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">ES</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">FR</p></th></tr></thead><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Portfolios</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td><td class="op-uc-table--cell"><p class="op-uc-p">Carteras/Portafolios</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Programs</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td><td class="op-uc-table--cell"><p class="op-uc-p">Programas</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Workspaces</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td><td class="op-uc-table--cell"><p class="op-uc-p">Espacios de trabajo</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr></tbody></table></figure>
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** access portfolios easily in OpenProject
**so that** I can have a quick overview on what portfolio I need to work next
**Acceptance criteria**
* A new global module is created named `Portfolios`
* It has entry points in both global sidebar and grid icon for global menu
* The current `Project lists` module is renamed to `Workspaces`
* Inside the portfolios' module, there are four views/queries that are not editable:
* All portfolios
* My portfolios
* Favourite portfolios
* Archived portfolios
* The user cannot save personalised queries or views
* The view can be filtered, searched and sort (by the sort by button on the more icon). On top of that, users can create new portfolios.
* In each view, in the content, an index page to access portfolios will be created with a new border box component based in Primer. Each border box element will contain the following information:
* Portfolio name
* Portfolio status (_\[open\]_ should it be editable?)
* Portfolio description
* Progress bar with sub-items status
* Favourite indication (Transparent IconButton star)
* Amount of programs in the portfolio
* Amount of project in the portfolio
* Budget information including total budget and budget spent
* Last updated
* The progress bar with the status should have a hover card with the index details
* The sort by functionality is extracted from the current implementation of `Project lists`
* Creating a new portfolio opens the form for portfolio creation based on the project creation one.
**Technical notes**
* <br>
**Permissions and visibility considerations**
* For
* `create portfolios` (##66612)
* Any permission in an active portfolio.
* For
* _\[open\]_ If a user can't `create portfolios`, should he see
* That might mean, that a member of a program or project cannot
* The user can
* Can create
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">EN</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">DE</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">ES</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">FR</p></th></tr></thead><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Portfolios</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td><td class="op-uc-table--cell"><p class="op-uc-p">Carteras/Portafolios</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Programs</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td><td class="op-uc-table--cell"><p class="op-uc-p">Programas</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell"><p class="op-uc-p">Workspaces</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td><td class="op-uc-table--cell"><p class="op-uc-p">Espacios de trabajo</p></td><td class="op-uc-table--cell"><p class="op-uc-p"><br data-cke-filler="true"></p></td></tr></tbody></table></figure>
**Out of scope**
* <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._