# Feature OP-20339 - Allow multiple assignees and individual estimated hours per role/user on a single ticket  Description

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

## 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 | Modules and project features / Work packages |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| 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

In modern cross-functional software development, a single work package or feature often requires simultaneous or tightly coupled collaboration across multiple disciplines, such as Design, Frontend/Backend Development, and Quality Assurance (QA).

Requiring separate child tickets for every minor contribution adds administrative overhead and clutters the board. Furthermore, for cross-project resource management (e.g., using the Team Planner), managers need to allocate specific estimated hours to individual team members or roles within that single ticket so that capacity planning remains accurate.

**User Story**  
AS AN OpenProject user working in a cross-functional team

I WANT to assign multiple team members to a single work package and allocate/track estimated hours per person or role

SO THAT multiple colleagues (e.g., Designers, Developers, QA) can collaborate on one task, log their hours independently, and appear accurately in capacity planning tools like the Team Planner.

**Acceptance Criteria**  
1\. Multiple Assignees: The &quot;Assignee&quot; field allows adding multiple users (or assigning specific users per role, e.g., Designer, Developer, QA) to a ticket.   
2\. Individual Hour Allocations: Users can specify estimated time per assignee/role on the ticket (e.g., 2 hours for Design, 8 hours for Development, 2 hours for QA).   
Current Behavior  
Currently, OpenProject strictly enforces a single user in the &quot;Assignee&quot; field per work package.

To involve multiple colleagues and track their time separately, teams are forced to either:

\* Create multiple child sub-tasks under a parent task (causing ticket clutter).   
\* Continually reassign the single ticket from one person to another throughout its lifecycle, making simultaneous collaboration and capacity planning in the Team Planner impossible.
