# Feature OP-20442 - Remove project summary page/link from work package default filters.

Project: OpenProject
Status: in development
URL: https://community.openproject.org/work_packages/OP-20442

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| 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 |  |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan | Community (COM) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Pavel Balashou |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a project member  
**I don't want to** see Summary link mixed in the list of default work package queries  
**So** I am not confused, because I expect it behave like a query.

**Acceptance criteria**

*   Summary link is not part of the project default wp query list.
    
*   The following routes respond with 404
    
    *   `/projects/{PROJECT_ID}/work_packages/report?name=summary`
        
    *   `/projects/{PROJECT_ID}/work_packages/report/type`
        
    *   `/projects/{PROJECT_ID}/work_packages/report/priority`
        
    *   `/projects/{PROJECT_ID}/work_packages/report/responsible`
        

<br>

**Motivation**

*   Summary link is mixed with wp filters in the project default wp filters list. The UX is confusing for users. I expect it to be another filter, but the behavior is completely different.
    
*   <img class="image_resized op-uc-image op-uc-image_inline" style="width:336px;" src="/api/v3/attachments/925611/content"><img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/925612/content">
    
*   It seems to be not used by anyone.
    
*   The code behind it is quite old.
    
*   After discussing it with Marc we agreed to remove this functionality. Jens is up for removal. Wieland was not sure.
    

<br>