Arbitrarily reorder namespaces, lists and tasks
The api now supports sorting by a position attribute - all thats left is the frontend implementation.
@konrad Tasks have the
position parameters which could probably be used this, but it's not available as a parameter for sorting according to the docs.
Maybe I'm missing something, but I don't see a way to change the order of lists/namespaces/buckets, as they don't have
position or a similar field where can arbitrary order be stored.
Now when I think about it, it seems that single
position parameter for task will be problematic when you want to have tasks sorted differently in list and in kanban buckets.
position could be used for sorting with a few small adjustments, that's not the hard problem. I'm open to suggestions for solutions to the "real" problem you identified in the second comment :)
Lists/Namespaces/Buckets would need to have that parameter added but again, wouldn't be that much of a deal.
Maybe the current
position field could be changed to
kanbanPosition and a new field called
listPosition could be added. Each field would hold position for their respective views.
I think that could work.
Thanks, it seems to work nicely. This feature makes a big difference.
I've just noticed the issue of not being able to reorder outside the boundaries of the current page in a paginated list view.
I don't even know what to suggest for that.
@SteveDinn I think the only way to really fix that would be to rework the pagination to an infinite scrolling thing instead of the "classic" pagination but that would bring up new problems. May be worth considering though.
Yeah, there are def. advantages to both. With infinite scroll, its a pain to get to the end of the list. Even moving an item before or after one that's not currently on the screen (but the same page) is not that great either. infinite scrolling would amplify that.
I really dont know what the right thing to do here is.
Deleting a branch is permanent. It CANNOT be undone. Continue?