# Feature OP-7902 - Group work packages in list view by custom field of type user

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Product Backlog |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| 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 | Jens Ulferts |
| 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

OpenProject is missing the feature to group by custom fields of type user. The goal is to have it similar to the Assignee field.

This would allow use cases from the capacity management (e.g. to see the available capacity). The advantage of a custom field is the availability of multi-selection. The alternative could be to allow for multiple Assignees per work package.

  

  

  

<figure class="image"><img src="/api/v3/attachments/19765/content"></figure>
