# Feature OP-20023 - [Work packages] Add "Work" and "Remaining work" to the bulk edit form

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

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

AS a planner maintaining recurring maintenance/upgrade projects  
I WANT to set the &quot;Work&quot; (estimated time) field on many work packages at once  
&nbsp; via the existing bulk edit form  
SO THAT I can apply a standard estimate to a whole class of tasks without  
  opening and editing each work package individually.

Use case:

We run recurring infrastructure upgrade cycles in a self-hosted OpenProject  
instance. Each upgrade cycle generates dozens to hundreds of work packages  
following a fixed pattern per resource: planning, execution, review.

The estimate for each step is a known constant that depends on the step and  
on the resource type, for example:  
\- Planning: 15 min (all resource types)  
\- Execution: 2 h for a simple VM, 4 h for an ESXi host  
\- Review: 15 min for a VM, 30 min for an ESXi host

Today these values must be entered one work package at a time. For a cycle  
covering 100 resources that is several hundred manual edits per cycle, which  
is time-consuming and error-prone, and it discourages maintaining estimates  
at all — which in turn makes capacity planning and the Work/Remaining work/  
% Complete progress reporting much less useful.

With Work available in the bulk edit form, the workflow becomes: filter the  
table to one class of tasks (e.g. type = Task, resource type = VM,  
step = Execution), select all, bulk edit, set Work = 2h. A handful of  
filter-and-set passes replaces hundreds of individual edits.

Note: this request is deliberately narrow. It does not ask for rule-based or  
per-type default estimates — filtering the table already gives us the  
&quot;different value per resource type&quot; behaviour, provided the field itself is  
bulk-editable.

**Acceptance criteria**

\- The bulk edit form (work package table -&gt; select multiple -&gt; right click -&gt;  
 &quot;Bulk edit&quot;) contains an input for &quot;Work&quot;, alongside the existing  
 attributes.  
\- Entering a value and submitting sets that value on all selected work  
 packages.  
\- Leaving the field empty leaves the existing value on each work package  
 unchanged, consistent with how the other fields in the bulk edit form  
 behave (&quot;(no change)&quot;).  
\- It is possible to clear the field on all selected work packages  
 (equivalent of &quot;(none)&quot;), consistent with other optional fields.  
\- &quot;Remaining work&quot; is handled the same way, so that the two values stay  
 consistent and % Complete is derived correctly.  
\- Work packages where the field is read-only (e.g. parents deriving the  
 value from their children, or types where the field is disabled in the  
 form configuration) are skipped, and the result screen reports which  
 work packages could not be updated — as it already does for other  
 failed bulk updates.  
\- Changes are written to the Activity of each affected work package.  
\- Existing bulk edit behaviour is unchanged, including the option to  
 suppress notifications for the update.

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
