github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-24 03:31:36 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #2400] reordering tasks not saved #6666

New Issue
Closed
opened 2026-04-20 17:15:21 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-20 17:15:21 -05:00
Owner
Copy Link

Originally created by @animismus on GitHub (Mar 16, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2400

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

When reordering a task in a list - moving the task up or down with the mouse - it does not get saved and upon entering a new task, the reorder task is back at its original position.
The workaround is to reorder the task, refresh the page, then add the new task.

Vikunja Version

2.1.0

Browser and version

firefox 148.0.2

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @animismus on GitHub (Mar 16, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2400 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description When reordering a task in a list - moving the task up or down with the mouse - it does not get saved and upon entering a new task, the reorder task is back at its original position. The workaround is to reorder the task, refresh the page, then add the new task. ### Vikunja Version 2.1.0 ### Browser and version firefox 148.0.2 ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror commented 2026-04-20 17:15:23 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 19, 2026):

So this only happens when you create a new task after reordering?

<!-- gh-comment-id:4088984138 --> @kolaente commented on GitHub (Mar 19, 2026): So this only happens when you create a new task after reordering?
GiteaMirror commented 2026-04-20 17:15:25 -05:00
Author
Owner
Copy Link

@animismus commented on GitHub (Mar 19, 2026):

So this only happens when you create a new task after reordering?

That was the use case I noticed. I just tested another thing:

  • reordering the task in Browser Window1
  • opening the same project in Browserwindow2. The task is reordered properly
  • add a task on BW1, the reordered task jumps down to the original position
  • add a task on BW2, the task is still ordered properly.

not sure if helpful.

<!-- gh-comment-id:4089527548 --> @animismus commented on GitHub (Mar 19, 2026): > So this only happens when you create a new task after reordering? That was the use case I noticed. I just tested another thing: - reordering the task in Browser Window1 - opening the same project in Browserwindow2. The task is reordered properly - add a task on BW1, the reordered task jumps down to the original position - add a task on BW2, the task is still ordered properly. not sure if helpful.
GiteaMirror commented 2026-04-20 17:15:26 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Mar 19, 2026):

All reproduced on the demo?

<!-- gh-comment-id:4090571763 --> @kolaente commented on GitHub (Mar 19, 2026): All reproduced on the demo?
GiteaMirror commented 2026-04-20 17:15:27 -05:00
Author
Owner
Copy Link

@animismus commented on GitHub (Mar 20, 2026):

All reproduced on the demo?

Sorry. Yes, I just tested this on the demo as well.

<!-- gh-comment-id:4096516528 --> @animismus commented on GitHub (Mar 20, 2026): > All reproduced on the demo? Sorry. Yes, I just tested this on the demo as well.
GiteaMirror commented 2026-04-20 17:15:28 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Apr 3, 2026):

This issue has been fixed in #2530, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

<!-- gh-comment-id:4184430296 --> @vikunja-bot-app[bot] commented on GitHub (Apr 3, 2026): This issue has been fixed in #2530, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6666
Delete Branch "%!s()"

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?