# Epic OP-7252 - Edit work package list without loading disruption

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

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Votes | 6 |
| List |  |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

| ID | Type | Subject | Status | Assignee | Target versions | Project | Priority | Spent time |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| OP-7260 | Feature | Improve slow work package table during drag & drop, and child creation | new |  | Wish List | OpenProject | Medium |  |

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Designer |  |
| Developers |  |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

### User Problem

#### User

Everybody editing work packages within the work package list among which are

  - Project manager
  - Project member
  - Product owner

#### Problem

The whole table (+ gantt) is currently reloaded whenever a user alters a work package within the list. This reload is slow and (in part) blocking.

  - User having to wait for the table to refresh.
  - User having their already opened input closed unexpectedly by a table refresh.

#### Pain

  - Wait

### Solution

*Avoid the refresh to become visible to the user*

This represents the current state of the discussion

  - After every update, fetch the data (same as before)
  - Instead of repainting the whole table, only repaint individual rows. In order to know which rows need repainting, we can store the lock version and the id in the front end and compare the values.
      - The repainting of individual rows will be fast compared to repainting the entire table.
      - The repainting of individual rows will lead to not closing fields already opened by the user in the meantime.
  - This approach has the drawback that in some cases, e.g. changing the attribute the work packages are grouped or filtered by, a work package might end up in the wrong place. Additionally, group counters & sums might be wrong. We have to identify whether this is acceptable. To mitigate the problem, we could display an icon showing that some data might be placed incorrectly. Ideally, we would highlight the elements that are invalid. The user can force refreshing the whole table by clicking on the icon.
      - To think about: If we accept the drawback of having incorrect positions, we could use this to our advantage by filtering by work package id and the updated at time (as well as the existing filters) to only fetch the work packages that have been updated since last we queried. This will lead to a considerable increase in backend performance in most cases as probably fewer work packages are returned than the whole page size.  

#### Out of Scope for the MVC

  - Backend speed improvements

#### Differentiation

  - An uninhibited flow when updating a set of work packages

#### Next iteration

  - Backend speed improvements (signaling and JSON rendering in DB)

### Launch and Growth

#### Measures

  - No more complaints about edit fields being closed unexpectedly
  - No more complaints about poor performance when editing fields in the wp table.

#### Messaging

*If you were to write a press release, how would you describe the value to customers?*

<figure class="table"><table><tbody><tr><th>Headline</th><td></td></tr><tr><th>First Paragraph</th><td></td></tr><tr><th>Customer Quote</th><td></td></tr></tbody></table></figure>

#### Go to market

*How are you planning on getting this into users' hands?*
