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

Begin of the insertionThis represents the current state of the discussion

End of the insertion * Begin of the insertionAfter every update, fetch the data (same as before)
* InsteadEnd of the insertion Begin of the deletion We only refresh partsEnd of the deletion of Begin of the insertionrepaintingEnd of the insertion the Begin of the insertionwhole table, only repaint individual rows. In order to knowEnd of the insertion Begin of the deletion table (thatEnd of the deletion which Begin of the insertionrows need repainting,End of the insertion we Begin of the insertioncan store the lock version and the id in the front end and compare the values.
End of the insertion Begin of the deletion know is outdated)
End of the deletion * Begin of the insertionThe repainting of individual rows will be fast compared to repainting the entire table.
* The repainting of individual rows will lead toEnd of the insertion Begin of the deletion We doEnd of the deletion not Begin of the insertionclosingEnd of the insertion Begin of the deletion close open editEnd of the deletion fields Begin of the insertionalready opened byEnd of the insertion Begin of the deletion (as we do not refreshEnd of the deletion the Begin of the insertionuser in the meantime.End of the insertion Begin of the deletion whole table but only individual rows)End of the deletion
* Begin of the insertionThis approach hasEnd of the insertion Begin of the deletion (Optionally) We do not refreshEnd of the deletion the Begin of the insertiondrawback that in some cases, e.g. changingEnd of the insertion Begin of the deletion whole ofEnd of the deletion the Begin of the insertionattributeEnd of the insertion Begin of the deletion table at all as this also leads to users loosingEnd of the deletion the work Begin of the insertionpackages are grouped or filtered by, aEnd of the insertion Begin of the deletion package they where just working at (e.g. added newEnd of the deletion work Begin of the insertionpackage 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,End of the insertion Begin of the deletion package, changing position because of grouping). Instead,End of the deletion we Begin of the insertioncould display an icon showing that some data might be placed incorrectly. Ideally, we would highlightEnd of the insertion Begin of the deletion add a notification (e.g. bubble) informingEnd of the deletion the Begin of the insertionelementsEnd of the insertion Begin of the deletion userEnd of the deletion that Begin of the insertionare invalid. The user can force refreshingEnd of the insertion the Begin of the insertionwholeEnd of the insertion table Begin of the insertionby clicking onEnd of the insertion Begin of the deletion is outdated, possibly indicatingEnd of the deletion the Begin of the insertionicon.
* To think about: If we accept the drawback of having incorrect positions, we could use this to our advantage by filtering byEnd of the insertion work Begin of the insertionpackage id and the updated at time (as well as the existing filters) to only fetch the workEnd of the insertion packages that have Begin of the insertionbeen updated since last we queried. This will lead toEnd of the insertion Begin of the deletion become outdated. Only if the user actively requestsEnd of the deletion a Begin of the insertionconsiderable increase in backend performance in most cases as probably fewer work packages are returned thanEnd of the insertion Begin of the deletion refresh, isEnd of the deletion the whole Begin of the insertionpage size.  End of the insertion Begin of the deletion of the table refreshed. End of the deletion

#### 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&#39; hands?_