# Feature OP-8504 - Global filter for work packages for non-global work package custom fields, versions, and categories

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 17 |
| 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 | Modules and project features / Query and filter |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Jens Ulferts |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** an OpenProject user  
**I want to** be able to select work package custom field filters of projects I have access to on global work package list  
**so that** I can filter based on work package custom fields from global WP list.

**Acceptance criteria**

*   Display work package custom fields activated in (at least one) projects in the global work package list if user is member of project.
*   Allow other local values as well (versions, categories)

**Context**

*   Currently, only WP custom fields are activated for all projects are shown as a filter option in the work package filter list on the global work package page.
*   Custom fields activated in single projects are not available as a filter which limits users.
    *   Custom field names could contain sensitive information, therefore ideally these custom fields should only be shown as an option for users who have access to these projects.