# Feature OP-10719 - have more work package related information available when finding/referencing existing work packages than only crwaling through WP-IDs and todays manually entered WP-Subjects

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

## 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 |  |
| 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** a _User_  
**I want to** have more work package related information available when finding/referencing existing work packages than only searching into WP-IDs and todays manually entered WP-Subjects - i.e. a separate list of key words / tag fields coming from the standard work package fields and work package related custom fields which are included in the referencing process (&quot;add existing child&quot; etc. )  
**so that** I can find existing workpackages much faster and convenient when finding/referencing  existing work packages in descriptions, wiki pages and when creating relations between work packages.

**Acceptance criteria**

*   finding existing work packages when referencing  them in descriptions, wiki pages and when creating relations between work packages provides more &quot;search results&quot; than only crawling throuch WP-ID and todays WP-Subject. 
    *   if there is a pragmatic way to optionally &quot;enrich&quot; the existing subject field programatically with the content of the mentioned &quot;list of key words&quot;/tags
        *   (this would act as a kind of &quot;content inception&quot; to the existing &quot;match code search&quot; through the WP subject field)
