# Feature OP-8925 - Process bulk editing and moving of work packages in background

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

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| 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 |  |
| 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** an OpenProject system administrator  
**I want** the bulk editing and moving of work packages to be processed in the background rather than in-request  
**so that** connections aren't blocked for 10+ seconds and so that it cannot happen that requests get cancelled altogether due to timeouts, causing a bad user experience.

**Acceptance criteria**

  - BulkController actions processed in background
  - MovesController actions processed in background
  - Progress shown to user even if it's and indeterminate spinner

I think this would be a good idea looking at the average durations we are observing:

<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/21825/content"></div><figcaption class="op-uc-figure--description">Request durations over 24 hours. Numbers: count, avg, p75, p95</figcaption></figure>
