tasks do not follow anymore the order #2064

Closed
opened 2023-07-20 09:16:39 +00:00 by asarubbo · 4 comments

Description

Hello, we are experiencing this issue since we updated to vikunja-0.21.0

Before 0.21.0, when we add a new task in a bucket, usually it was positioned at the bottom, while now it seems that it goes in a radom position.

Considering the uploaded screenshot, I expect to see (from top to bottom):
#326
#333
#334
#335

While we have (without have touched them):
#333
#335
#334
#326

Vikunja Frontend Version

0.21.0

Vikunja API Version

0.21.0

Browser and version

Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.3

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

### Description Hello, we are experiencing this issue since we updated to vikunja-0.21.0 Before 0.21.0, when we add a new task in a bucket, usually it was positioned at the bottom, while now it seems that it goes in a radom position. Considering the uploaded screenshot, I expect to see (from top to bottom): #326 #333 #334 #335 While we have (without have touched them): #333 #335 #334 #326 ### Vikunja Frontend Version 0.21.0 ### Vikunja API Version 0.21.0 ### Browser and version Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.3 ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
asarubbo added the
kind/bug
label 2023-07-20 09:16:39 +00:00
Owner

Is this with a bucket with a lot of tasks? Does it happen if you create a new bucket with only 5 tasks in it?

Is this with a bucket with a lot of tasks? Does it happen if you create a new bucket with only 5 tasks in it?
Author

Hi,

the bucket contains only the four tasks you can see in the screenshot.

I tested in a new bucket and it didn't happen, but my guess is that it is a completely random issue.

Hi, the bucket contains only the four tasks you can see in the screenshot. I tested in a new bucket and it didn't happen, but my guess is that it is a completely random issue.
Owner

Can you check in the db if the kanban_position column represents the order you see in the frontend? And how it behaves if you create a new task?

Can you check in the db if the `kanban_position` column represents the order you see in the frontend? And how it behaves if you create a new task?
Owner

Closing due to inactivity. Please ping with more information.

Closing due to inactivity. Please ping with more information.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/vikunja#2064
No description provided.