Content
View differences
Updated by Jens Ulferts almost 6 years ago
### 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_
* We only refresh parts of the table (that which we know is outdated)
* We do not close open edit fields (as we do not refresh the whole table but only individual rows)
* (Optionally) We do not refresh the whole of the table at all as this also leads to users loosing the work package they where just working at (e.g. added new work package, changing position because of grouping). Instead, we add a notification (e.g. bubble) informing the user that the table is outdated, possibly indicating the work packages that have become outdated. Only if the user actively requests a refresh, is the whole of the table refreshed.
#### 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?_
#### 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_
* We only refresh parts of the table (that which we know is outdated)
* We do not close open edit fields (as we do not refresh the whole table but only individual rows)
* (Optionally) We do not refresh the whole of the table at all as this also leads to users loosing the work package they where just working at (e.g. added new work package, changing position because of grouping). Instead, we add a notification (e.g. bubble) informing the user that the table is outdated, possibly indicating the work packages that have become outdated. Only if the user actively requests a refresh, is the whole of the table refreshed.
#### 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?_