Content
View differences
Updated by Niels Lindenthal 10 months ago
**As** a project organization
**I want to** be able to organise my projects in portfolios and programs
**so that** I can organise and track them better. better
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/743718/content"> ### **Acceptance criteria**
<br>
* Project admins can group projects and put them in a portfolio (a group of projects)
* Portfolios themselves to be organised into a higher level: programs
* Introduce the idea of **organisational unit** (OU)
* A group of users with a specific function
* An organisational unit can be named
* It should be possible to use an OU as a resourcing unit (time and costs)
* It should be possible to assign a project to an organisational unit
### **Open questions**
* Do we really need two levels (portfolio and programs)? What are the differences in terms:
* what kinds of information/attributes for each level
* what kind of actions available for both
* Does a project _belong to_ a single portfolio or program, or can be assigned to multiple ones?
* How should these structures affect reporting, progress tracking, and logging time and costs?
* How do portfolios and projects affect roles and permissions?
* Are there portfolio-/project-specific roles and permissions?
* Can permissions _trickle down?_ (As in, a user that has permission A in operational unit X will also get permission A in a project that the OU has been assigned to, even if the user doesn't directly have those permissions at a project level?)
**I want to** be able to organise my projects in portfolios and programs
**so that** I can organise and track them better.
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/743718/content">
<br>
* Portfolios themselves to be organised into a higher level: programs
* Introduce the idea of **organisational unit** (OU)
* A group of users with a specific function
* An organisational unit can be named
* It should be possible to use an OU as a resourcing unit (time and costs)
* It should be possible to assign a project to an organisational unit
###
* Do we really need two levels (portfolio and programs)? What are the differences in terms:
* what kinds of information/attributes for each level
* what kind of actions available for both
* Does a project _belong to_ a single portfolio or program, or can be assigned to multiple ones?
* How should these structures affect reporting, progress tracking, and logging time and costs?
* How do portfolios and projects affect roles and permissions?
* Are there portfolio-/project-specific roles and permissions?
* Can permissions _trickle down?_ (As in, a user that has permission A in operational unit X will also get permission A in a project that the OU has been assigned to, even if the user doesn't directly have those permissions at a project level?)