# Feature SPPM-217 - Limit hierarchy options based on workspace type

Project: Stream Project Portfolio Management
Status: closed
URL: https://community.openproject.org/work_packages/SPPM-217

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 17.0.0 |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

| ID | Subject | Type | Status | Assignee | Target versions | Spent time |
| --- | --- | --- | --- | --- | --- | --- |
| SPPM-259 | Limit portfolios to not allow subportfolios | Implementation | closed |  | 17.0.0 |  |

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| SPPM-267 | Bug | It's possible to define a default template for sub portfolios | closed |  | 17.0.0 |  | Modules and project features / Portfolio |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | Ivan Kuchin |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**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 (<mention class="mention" data-id="60623" data-type="work_package" data-text="###60623">###60623</mention> and <mention class="mention" data-id="63544" data-type="work_package" data-text="###63544">###63544</mention>). 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.*