# Epic OP-7147 - Use more sophisticated Work Package autocompleter

Project: OpenProject
Status: in specification
URL: https://community.openproject.org/work_packages/OP-7147

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Votes |  |
| List |  |
| Target versions | Product Backlog |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

| ID | Type | Subject | Status | Assignee | Target versions | Project | Priority | Spent time |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| OP-7148 | Feature | Generalise WP autocompleter from time logging module | new |  | Wish List | OpenProject | Medium |  |
| OP-7149 | Feature | Use generic WP autocompleter for the relations tab | new |  | Wish List | OpenProject | Medium |  |
| OP-7150 | Feature | Use generic WP autocompleter within the Boards module | new |  | Wish List | OpenProject | Medium |  |

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Designer |  |
| Developers |  |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

### Pain point

*   When using the WP autocompleter e.g. in the relations tab or the boards module, I can only find the WP if I know the ID or a large part of the title.
*   Often I have to use the main search to know the ID, so that I can then, add the WP.

### Solution

In the time logging modal, we already have a better autocompleter which has the option to scroll through the most recently used WPs.

We could use this component at other places, too.

### Acceptance criteria

*   The autocompleter from the time logging widget is generalised so that it can be used at other places, too.
*   The generic component should be used at different places (see child tickets)
