Page MenuHomePhabricator

Animate changes to workboards
Closed, WontfixPublic


Now or in the future, some types of edits cause nonlocal changes or nonlocal card movement. For example:

  • After T4900, any card can move to any position on the workboard.
  • After T10334, dragging a card to a column (vs a specific place) may reorder it to a different location after you drop it.
  • Editing a card and changing its priority or assignee (after T10333) may cause it to reorder.
  • Creating a task may populate it anywhere in the column, or even on other columns if you change tags.
  • Any edit may pull data from concurrent edits and cause column reordering (e.g., another user changes the priority of task A, then you upload a cover photo to task B). We might want to suppress re-sorting on redraw for updates like cover updates, but other edits we can't suppress.
  • Editing a task and removing or changing projects may remove it from the board or fling it across columns.

In all cases, it may be difficult for users to visually parse what's going on.

Some simple animation (fading cards out, fading cards in, glowing cards when they update) could help make the board more readable during changes.

We might be able to do more complex animations, too (zooming cards around, transitioning cards), although I'm not sure how necessary or achievable they are.

It's possible we don't really need this, but I suspect some edits will be hard to read/parse after T4900.

It's also possible that this will be a huge problem and we need more (an edit feed so you can read what has happened?) or similar, although I suspect this won't be the case.

Event Timeline

epriestley claimed this task.

We may still pursue this, especially after T4900, but a lot of the use cases / needs are mostly theoretical and it's not clear they're actually necessary. Some of the actual solutions (like T10335) may largely provide enough clarity about these cases on their own. I'm currently planning to wait for feedback about recent and near-future changes (including triggers) and then fix whatever issues arise surgically -- possibly through animation, but possibly through other UI/UX remedies.