# Feature OP-18872 - Block the parent work package relation when a linked workpackage is unresolved

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

## 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, Modules and project features / Relations and scheduling |
| 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 | OP Dev Sirius Team |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** User  
**I want to** :  
  
We use work packages of type Defect to track issues. Each Defect is linked via a relation to an overarching parent work package that is managed by Development in a different project.  
  
When a Defect remains unresolved, the relation to the parent work package is still considered “active/usable”. This can lead to situations where the parent work package is treated as unblocked even though an open Defect exists.  
  
**Requested feature / Expected behavior**  
If a linked **Defect** is **unresolved**, the **relation on the parent work package must be blocked** (i.e., the parent work package should be flagged as blocked by that Defect).

*   The blocking should apply to parent work packages located in other projects as well.
    
*   Once the Defect is moved to a **resolved/closed** state, the blocking should be removed automatically.
    
*   The behavior works consistently for all relevant unresolved statuses (e.g., _New, Open, In Progress_), and respects the configured resolved/closed statuses.
    

<br>

**Acceptance criteria**

*   Given a Defect linked to a parent work package (cross-project), when the Defect status is **unresolved**, the parent work package shows the relation as **blocked** / is considered **blocked by the Defect**.
    
*   When the Defect status changes to **resolved/closed**, the parent work package is **unblocked** automatically.
    

**Technical notes**

*   <br>
    

**Permissions and visibility considerations**

*   _To whom is this feature visible?_
    
*   _When is it not visible?_
    

**Translation considerations**

*   _Key terms and phrases in the key languages_&nbsp;
    

**Out of scope**

*   <br>
    

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