# Feature OP-2651 - Constraints in work package hierarchy

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| 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 |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As an** User  
**I want to** define that specific workpackages (types) can have just childs of specific workpackages (types)  
**So that i** can ensure a high methodical consistency of the workpackage hierarchy

use case (example):

  - a user wants do define three types of a workpackage (“a”, “b”, “c”)
      - “a” can only have “a” and “b” as child (nice to have: + “a” can not be without child)
      - “b” can only have “c” as child
      - “c” can not have any childs

https://community.openproject.org/topics/5921 (the “verion-issue” mentioned in this discussion as well isn’t that important)
