# Feature OP-18803 - Option to hide closed work packages in relations and child work package sections

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

## 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 / 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\*\* a user working with work package hierarchies and relations in OpenProject &nbsp;  
\*\*I want to\*\* hide closed work packages in the Relations and Child work packages section  
\*\*so that\*\* I have a clearer overview and can focus on active work during planning

\---

\### Acceptance criteria

\- A main control to hide/show closed work packages is available    
\- When “Hide closed work packages” is enabled, work packages in a \*closed\* status are not shown in these sections.  
\- When “Hide closed work packages” is disabled, all related and child work packages are shown (current behavior).  
\- Counts/indicators (e.g., number of relations/children) are updated to reflect only visible work packages or clearly indicate that some are hidden.  
\- The feature does not change which work packages a user is allowed to access; it only affects visibility within these UI sections.

\---

\### Technical notes

\- Reuse the existing status concept: use the “is\_closed” flag on statuses to determine which work packages are considered closed.  
\- Implement a per-user, per-project preference (e.g., via user preferences or project-specific settings) to persist the toggle state.  
\- UI proposal:  
 - Add a checkbox or toggle (e.g., “Hide closed work packages”) in the header area of the Relations and Children sections.  
 - Optional: an info indicator (e.g., “3 closed work packages hidden”) when the filter is active.  
\- Ensure no additional queries are triggered per row; integrate the closed-status filtering into the existing data retrieval layer for relations and children.  
\- Include automated tests:  
 - Unit tests for filtering logic (open vs. closed).  
 - Integration/UI tests for the toggle state and persistence.

\---

\### Permissions and visibility considerations

\- \*\*To whom is this feature visible?\*\*    
 - All users who can view work packages and their relations/children in a project.  
\- \*\*When is it not visible?\*\*    
 - When the user does not have permission to view work packages in the project.

\---

\### Translation considerations

Key terms and phrases:

\- English    
 - “Hide closed work packages”    
 - “Show closed work packages”    
 - “Closed work packages hidden”    
 - “Relations”    
 - “Child work packages”  
\- German    
 - “Abgeschlossene Arbeitspakete ausblenden”    
 - “Abgeschlossene Arbeitspakete einblenden”    
 - “Abgeschlossene Arbeitspakete ausgeblendet”    
 - “Beziehungen”    
 - “Untergeordnete Arbeitspakete”

\---

\### Out of scope

\- Changing the definition or configuration of “closed” statuses.  
\- Archiving, deleting, or otherwise altering closed work packages.  
\- Introducing new global admin settings for this behavior beyond the per-user/per-project toggle.  
\- Changes to API responses for relations or child work packages (filtering is a UI concern only).
