github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-08 12:57:52 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #2618] Recurring events are not correctly moved in kanban #6713

New Issue
Closed
opened 2026-04-20 17:17:40 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 17:17:40 -05:00
Owner
Copy Link

Originally created by @axos88 on GitHub (Apr 13, 2026).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2618

Pre-submission checklist

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

Description

Repro:

  • Create a recurring task, 7 days from completion, set due time to something like tomorrow
  • open kanban view
  • drag task to done bucket

Expected:

  • task goes back to backlog, and dates are updated

Actual:

  • dates are updated, task does not go back to backlog. On page refresh it is moved, so it's a UI update bug.

Vikunja Version

i guess latest, just playing with the demo

Browser and version

chrome, linux

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @axos88 on GitHub (Apr 13, 2026). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/2618 ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description Repro: - Create a recurring task, 7 days from completion, set due time to something like tomorrow - open kanban view - drag task to done bucket Expected: - task goes back to backlog, and dates are updated Actual: - dates are updated, task does not go back to backlog. On page refresh it is moved, so it's a UI update bug. ### Vikunja Version i guess latest, just playing with the demo ### Browser and version chrome, linux ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror added the area/kanbanarea/recurring-tasksconcern/ux labels 2026-04-20 17:17:40 -05:00
GiteaMirror commented 2026-04-20 17:17:43 -05:00
Author
Owner
Copy Link

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

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

<!-- gh-comment-id:4243586868 --> @vikunja-bot-app[bot] commented on GitHub (Apr 14, 2026): This issue has been fixed in #2621, 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 area/kanban area/recurring-tasks concern/ux
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#6713
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?