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

[PR #2574] [MERGED] fix: route recurring tasks to default bucket when marked done #5741

New Issue
Closed
opened 2026-04-16 13:50:52 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-16 13:50:52 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/go-vikunja/vikunja/pull/2574
Author: @tink-bot
Created: 4/9/2026
Status: ✅ Merged
Merged: 4/9/2026
Merged by: @kolaente

Base: main ← Head: fix-recurring-task-bucket-on-done

📝 Commits (6)

  • ada15c0 test(kanban): add failing test for repeating task bucket routing on done (#2573)
  • 91fa5bf fix(kanban): route repeating tasks to default bucket when dropped on done (#2573)
  • 3bfe2b1 test(tasks): add failing test for repeating task bucket routing via Task.Update (#2573)
  • 27a5c15 refactor(tasks): add moveTaskToDefaultBuckets helper (#2573)
  • 962badc fix(tasks): route repeating tasks to default bucket when marked done (#2573)
  • 38322ae fix(kanban): skip upsert when repeating task already in default bucket (#2573)

📊 Changes

4 files changed (+157 additions, -3 deletions)

View changed files

📝 pkg/models/kanban_task_bucket.go (+14 -2)
📝 pkg/models/kanban_task_bucket_test.go (+50 -0)
📝 pkg/models/tasks.go (+47 -1)
📝 pkg/models/tasks_test.go (+46 -0)

📄 Description

When a recurring task was marked done from a kanban board, it stayed in its source column (e.g. "Doing") instead of moving back to the default "To-Do" column, so the next iteration wasn't visible where users expected it.

Fixes #2573

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/go-vikunja/vikunja/pull/2574 **Author:** [@tink-bot](https://github.com/tink-bot) **Created:** 4/9/2026 **Status:** ✅ Merged **Merged:** 4/9/2026 **Merged by:** [@kolaente](https://github.com/kolaente) **Base:** `main` ← **Head:** `fix-recurring-task-bucket-on-done` --- ### 📝 Commits (6) - [`ada15c0`](https://github.com/go-vikunja/vikunja/commit/ada15c024df0f3fd060b313f795b85b73eaee48d) test(kanban): add failing test for repeating task bucket routing on done (#2573) - [`91fa5bf`](https://github.com/go-vikunja/vikunja/commit/91fa5bfb3498e4b9a65aa0795d28590d7b141f07) fix(kanban): route repeating tasks to default bucket when dropped on done (#2573) - [`3bfe2b1`](https://github.com/go-vikunja/vikunja/commit/3bfe2b131fafcda38682b7bed699b3426f05f44c) test(tasks): add failing test for repeating task bucket routing via Task.Update (#2573) - [`27a5c15`](https://github.com/go-vikunja/vikunja/commit/27a5c15a97ded3d33dabbc66b87befc6a02c0536) refactor(tasks): add moveTaskToDefaultBuckets helper (#2573) - [`962badc`](https://github.com/go-vikunja/vikunja/commit/962badc5e5bc4f5d9fc421754fb8bd30d04e4974) fix(tasks): route repeating tasks to default bucket when marked done (#2573) - [`38322ae`](https://github.com/go-vikunja/vikunja/commit/38322aed70a810071a90b7361c884f01da16801e) fix(kanban): skip upsert when repeating task already in default bucket (#2573) ### 📊 Changes **4 files changed** (+157 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `pkg/models/kanban_task_bucket.go` (+14 -2) 📝 `pkg/models/kanban_task_bucket_test.go` (+50 -0) 📝 `pkg/models/tasks.go` (+47 -1) 📝 `pkg/models/tasks_test.go` (+46 -0) </details> ### 📄 Description When a recurring task was marked done from a kanban board, it stayed in its source column (e.g. "Doing") instead of moving back to the default "To-Do" column, so the next iteration wasn't visible where users expected it. Fixes #2573 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-16 13:50:52 -05:00
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 pull-request
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#5741
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?