# Epic OP-4398 - Unify autocomplete and multi-select fields

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

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

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

## Planning

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

## Subitems

_No work packages_

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

### Current



Currently we have different input fields:  

(for a detailed list, have a look at https://drive.google.com/file/d/1MX-AUwsE5m-NOeQRPth1ulSUUjloqYmh/view



**Column selection**



![](https://community.openproject.com/attachments/12700/grafik.png)



**Custom fields**



![](/api/v3/attachments/15231/content)



**Project**



![](/api/v3/attachments/15232/content)



### Expected



*   We should use the same autocompleter everywhere. This has multiple advantages:

    *   Users only have to handle one kind of field, making it easier to use.

    *   Easier maintenance as we only have to deal with one implementation

    *   We can reduce our amount of code.

*   Right now the ng-select is the most promising implementation and already used for the WP attributes, the search and the watchers.
