qgil wrote on 2014-04-23 21:05:24 (UTC)

Reported upstream, although not as an own task yet:

https://secure.phabricator.com/T4807#11

qgil wrote on 2014-04-23 23:39:36 (UTC)

The reply upstream basically says that tasks should move only when someone moves them. We are having many tester around these days (including ourselves), so maybe that's why.

qgil wrote on 2014-04-24 18:22:13 (UTC)

Resolving as invalid under the valid suspicion that these changes happen because someone else is moving your cards manually. Please reopen if you find a different pattern.

mattflaschen wrote on 2014-05-03 04:06:35 (UTC)

qgil:

The reply upstream basically says that tasks should move only when someone moves them.

The original report here is not that tasks move on their own, but that they don't save the moves when someone moves them. In other words, someone drags cards around, refreshing, and sometimes finds their dragging/prioritization work did not save.

I haven't reproduced this myself so far (but I haven't tested dragging a lot either), so I'm not re-opening. But we should keep an eye out for the problem.

Also, "We don't currently record internal priority changes so there's no way to see who has been doing this." (from upstream) is somewhat problematic (most of Phabricator is more transparent than that, as it should be).

However, I think their idea upstream of "things stay where I put them and position has no meaning outside of the board" seems interesting. Basically, task position on a workboard would vary by workboard and not be global.

qgil wrote on 2014-05-04 04:27:40 (UTC)

The original report here is not that tasks move on their own, but that they don't save the moves when someone moves them.

This may be true while the compass animation is still ongoing (that's the reasons for the animation to exist). In my experience, when the move is complete, it stays there.

importing issue status