# Feature OP-20338 - Enable a global and project-specific hierarchy structure of work packages

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-20338

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 2 |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Work packages |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Rosanna Sibora |
| Product manager | Sonita Soth |
| Feature Lead |  |
| Developers | OP Dev Comms Team |
| Designer | Parimal Satyal |
| Ordered by |  |
| Signed off by |  |
| Interest by | Home 2 (224196000004854001) |

## Estimates and progress

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

## Description

**As** an OpenProject admin  
**I want to** configure a common project-specific and global hierarchy structure of work packages &nbsp;e.g. Program level (contains...), project level (contains...) , team level (contains Epic, Story, Task, ...)  
**so that** i enable a unified work break down structure with fix parent-child relationships (e.g SAFe). The levels differs in the different responsibilities. Especially in bigger companies it is effective to provide a common way of planning and work break down structure to be aligned across different projects / programs and across different business units and organizational units.

Priority medium: Possible workaround is to implement a validation plugin to check/verify the user event.

**Acceptance criteria**

*   different hierarchy levels can be established in the admin section
    
*   one work package type can be assigned to one specific hierarchy level
    
*   parent-child structure 1-n
    
*   only valid relationships can be selected by the end user
    

**Technical notes**

*   <br>
    

**Permissions and visibility considerations**

*   OpenProject admins at global configuration section
    
*   end user is guided by the tool
    

**Translation considerations**

*   _Key terms and phrases in the key languages_
    

**Out of scope**

*   assignment/validation  responsibles in the project/program
    

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
