Skip to content

Bug: Recurring tasks are recreated in first bucket when no default bucket is set #2786

@sunilnc

Description

@sunilnc

Pre-submission checklist

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

Description

Description
When using recurring tasks in a project with multiple buckets, completed recurring tasks are recreated in the project's first bucket rather than in the bucket they originally belonged to.

This only happens when no bucket is configured as the project’s default bucket.

Expected behaviour
A recurring task should be recreated in the same bucket it was originally created in.

Actual behaviour
After completing a recurring task:

  • the new recurring instance is created
  • but it is placed into the first bucket in the project
  • instead of remaining in its original bucket

Steps to reproduce

  1. Create a project with multiple buckets
  2. Do not set any bucket as the default bucket
  3. Create recurring tasks in different buckets
  4. Complete one of the recurring tasks
  5. Observe that the recreated task appears in the first bucket instead of the original bucket

Additional notes
This feels unintuitive because the recurring task loses its workflow/category placement every time it is completed.

I have recorded a clip of my experience.

Vikunja Version

2.3.0

Browser and version

Firefox

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

Screen.Recording.2026-05-21.at.16.09.20.mov

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/kanbanKanban view, buckets, bucket CRUD, done-bucket behaviorarea/recurring-tasksRepeat rules, recurring task behavior, RRULEconcern/regressionWorked in a prior release, now brokenconcern/uxUX polish, ergonomics, workflow complaints without a clear bug

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions