# Epic OP-10361 - Consistent search fields throughout the application

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

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

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

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Votes |  |
| 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 | Niels Lindenthal |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Designer |  |
| Developers |  |
| Requested by |  |
| Interest by |  |

## Estimates and progress

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

## Description

https://www.openproject.org/docs/development/design-system/#search-field

**Open:**

1.  From the list what are considered search fields and what can be done with drop downs that are not searchable fields?
2.  Semantically define the search fields so it is clear for everyone what are search fields and what not.
    *   In this description also add the different variants that might occur in this search fields: with or without magnifier icon, with extra settings or not, dropdown with options before searching or not, is the list of results attached directly to the field or independent...
