Arbitrarily reorder namespaces, lists and tasks #1720
Labels
No Label
dependencies
duplicate
help wanted
invalid
kind/bug
kind/feature
needs reproduction
question
security
wontfix
No Milestone
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/vikunja#1720
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Preferably using drag-and-drop.
The api now supports sorting by a position attribute - all thats left is the frontend implementation.
@konrad How would you go about telling the API to change the order of lists (or other things)? I don't see a field for that in the docs...
@profi248 Oh there is: https://try.vikunja.io/api/v1/docs#tag/task/paths/~1lists~1{listID}~1tasks/get
Look for
sort_by
andorder_by
.@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 tokanbanPosition
and a new field calledlistPosition
could be added. Each field would hold position for their respective views.I think that could work.
Implemented in vikunja/frontend#620 and vikunja/api#923. A new unstable release containing the changes is already released, you can also test it on try.
Feel free to open a new issue or ping if you find something is not quite working.
Thanks, it seems to work nicely. This feature makes a big difference.
I've just noticed a bug with kanban though, will take a look at that tomorrow.
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.
Is this also not included in 0.18.2? :/
Can I move lists across namespaces with this?
yes :/
This only allows you to rearrange the lists in the menu, not move them between namespaces. There is a forum discussion about this but it's not implemented yet.