# Feature OP-7512 - Include custom field content in parent or child WP search/all search

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| 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 |  |

## 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

When searching for parent or child WPs in the &quot;Set parent&quot; field of a WP or when adding a child WP reference, it would be helpful if the search also considered custom field content of the WPs or their description.

Our use case is a custom &quot;Project ID&quot; where some WPs have an identifier to which project, sub-project, work package of the sub-project, etc they belong. The subject of the WP should contain only the subject, nothing else. Apart from identifying WPs the identifier is useful for sorting.

Without the ability to search for this ID everywhere it does not make sense to have it, because currently if one wants to assign a parent WP he\*she needs to know the subject.
