Content
View differences
Updated by Jens Ulferts 6 months ago
**As** a portfolio/program/project manager
**I want to** have sensible options when choosing the parent of a portfolio/program/project
**so that** I am not burdened by undesired choices and don't end up with a non sensical hierarchy
**Acceptance criteria**
* The options on portfolio/program/project creation and modification for which workspace item can become a parent are limited based on the type
* For project: all of portfolio, program and project
* For program: portfolio
* For portfolio: ~~portfolio~~ (outdated) none. A portfolio is always a root element.
* These are then the only options displayed when choosing the parent item
* Selecting a wrongful parent by any means (e.g. form manipulation) results in an error.
**Technical notes**
* <br>
**Permissions and visibility considerations**
* \[open\] there is currently the "+ Subproject" button in the project settings by which a new project can be created. That is governed by the "Create subprojects" permission for which feature requests are open designed to change the behaviour there (###60623 and ###63544). Either the features are implemented, or the permission for now allows to only create (sub-)projects or it allows to create all (sub-)workspace types.
**Translation considerations**
* _none_
**Out of scope**
* Providing specific options via the API. Since the feature is still behind a feature flag, only projects can be created so that should be ok.
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** have sensible options when choosing the parent of a portfolio/program/project
**so that** I am not burdened by undesired choices and don't end up with a non sensical hierarchy
**Acceptance criteria**
* The options on portfolio/program/project creation and modification for which workspace item can become a parent are limited based on the type
* For project: all of portfolio, program and project
* For program: portfolio
* For portfolio: ~~portfolio~~ (outdated) none. A portfolio is always a root element.
* These are then the only options displayed when choosing the parent item
* Selecting a wrongful parent by any means (e.g. form manipulation) results in an error.
**Technical notes**
* <br>
**Permissions and visibility considerations**
* \[open\] there is currently the "+ Subproject" button in the project settings by which a new project can be created. That is governed by the "Create subprojects" permission for which feature requests are open designed to change the behaviour there (###60623 and ###63544). Either the features are implemented, or the permission for now allows to only create (sub-)projects or it allows to create all (sub-)workspace types.
**Translation considerations**
* _none_
**Out of scope**
* Providing specific options via the API. Since the feature is still behind a feature flag, only projects can be created so that should be ok.
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._