# Feature OP-4302 - Better filtering of optional CustomFields

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

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

If CustomField is not marked as required then the fact that field may not be set at all should be taken into account.  
Missing filters:

1.  field set for all types
2.  field unset for all types (integers have an option to compare with –1, but that makes impossible to filter WPs with actual –1 in that field)
3.  \<, \>, \!=, “does not contain” filters should have two options — those that ignore WP with field unset (as it is now), and those that include WPs with field unset.

I will try to implement missing filters and contribute.
