Bug: Arbitrary order of tasks not persisted #84

Closed
opened 2025-11-01 20:46:30 -05:00 by GiteaMirror · 7 comments
Owner

Originally created by @refactoriel on GitHub (Sep 17, 2022).

In the frontend tasks can be arbitrarily ordered via drag and drop. Upon reload of the page the task order is back to sorted by creation. Maybe the manual ordering is not propagated to the backend?

Otherwise great app, enjoying working with it 😀

Originally created by @refactoriel on GitHub (Sep 17, 2022). In the frontend tasks can be arbitrarily ordered via drag and drop. Upon reload of the page the task order is back to sorted by creation. Maybe the manual ordering is not propagated to the backend? Otherwise great app, enjoying working with it 😀
GiteaMirror added the bug label 2025-11-01 20:46:30 -05:00
Author
Owner

@refactoriel commented on GitHub (Sep 17, 2022):

I increased log level to DEBUG and found the following. Dragging a task to another position successfully leads to a POST request. Unfortunately, I couldn't see the payload. The UPDATE statement to the database seems a little weird: The position values are 0 at some target locations and huge integers at others (this is in a list with 4 items).

@refactoriel commented on GitHub (Sep 17, 2022): I increased log level to DEBUG and found the following. Dragging a task to another position successfully leads to a POST request. Unfortunately, I couldn't see the payload. The UPDATE statement to the database seems a little weird: The position values are `0` at some target locations and huge integers at others (this is in a list with 4 items).
Author
Owner

@kolaente commented on GitHub (Sep 20, 2022):

The huge integers is what it should be. This allows putting a list between two others without needing to update every single one of them.

Can you reproduce this on try?

Is this your issue? https://kolaente.dev/vikunja/frontend/issues/2119#issue-7584

@kolaente commented on GitHub (Sep 20, 2022): The huge integers is what it should be. This allows putting a list between two others without needing to update every single one of them. Can you reproduce this on [try](https://try.vikunja.io)? Is this your issue? https://kolaente.dev/vikunja/frontend/issues/2119#issue-7584
Author
Owner

@refactoriel commented on GitHub (Sep 21, 2022):

On try it works. So it's probably fixed in the latest.

I'm running the latest versioned image, i.e. 0.19.1. Any ETA on when this fix will be available in a version?

@refactoriel commented on GitHub (Sep 21, 2022): On *try* it works. So it's probably fixed in the latest. I'm running the latest versioned image, i.e. 0.19.1. Any ETA on when this fix will be available in a version?
Author
Owner

@kolaente commented on GitHub (Sep 21, 2022):

No real ETA but there will be a version in the next few weeks.

I'll close this as fixed in the development branch, please ping if you have other issues.

@kolaente commented on GitHub (Sep 21, 2022): No real ETA but there will be a version in the next few weeks. I'll close this as fixed in the development branch, please ping if you have other issues.
Author
Owner

@refactoriel commented on GitHub (Sep 21, 2022):

I now actually tried the latest defined by sha256:4aeda57e0037e9f2db56f5706b7232c4252671657e74d35b9aa65feeac121d0f.

The issue is still there :(
Any ideas how I can debug it on my setup?

@refactoriel commented on GitHub (Sep 21, 2022): I now actually tried the `latest` defined by `sha256:4aeda57e0037e9f2db56f5706b7232c4252671657e74d35b9aa65feeac121d0f`. The issue is still there :( Any ideas how I can debug it on my setup?
Author
Owner

@kolaente commented on GitHub (Sep 21, 2022):

If you want to run the lastest unstable build, you'll need to use the unstable tag.

A bit more info in the docs: https://vikunja.io/docs/versions/

@kolaente commented on GitHub (Sep 21, 2022): If you want to run the lastest unstable build, you'll need to use the `unstable` tag. A bit more info in the docs: https://vikunja.io/docs/versions/
Author
Owner

@refactoriel commented on GitHub (Sep 21, 2022):

Turns out that it had already been fixed in the versioned image that I had used. Somehow my installation was broken, probably because I had imported a mysqldump from a test installation. Awesome that there actually is an export and import functionality. Makes it super smooth!

sorry for the noise

@refactoriel commented on GitHub (Sep 21, 2022): Turns out that it had already been fixed in the versioned image that I had used. Somehow my installation was broken, probably because I had imported a mysqldump from a test installation. Awesome that there actually is an export and import functionality. Makes it super smooth! sorry for the noise
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#84