New task in Kanban bucket reorders to top of bucket instead of remaining at bottom

Environment: Vikunja v2.1.0 (regression from v0.9 behavior)

Description: When creating a new task via the inline input at the bottom of a Kanban bucket, the newly created task reorders to the top of the bucket rather than remaining at the bottom where it was entered. In v0.9, the task remained at the bottom of the bucket, keeping it visible for immediate editing after the user had just typed out the task name at the bottom of the bucket.

Steps to reproduce:

  1. Open a project in Kanban view

  2. Navigate to a bucket with enough tasks to require scrolling

  3. Scroll to the bottom of the bucket

  4. Type a new task name and press Enter

  5. Observe: the new task reorders to the top of the bucket, no longer visible at the insertion point

Expected behavior: The new task should remain at the bottom of the bucket where it was created so the user can immediately open it to add details like notes, due dates, and labels.

Actual behavior: The new task reorders to the top of the bucket, requiring the user to scroll back up to locate and edit the task they just created.

Impact: For heavily populated buckets, this creates a disorienting workflow where every new task requires scrolling to find it immediately after creation to further edit the new taks. There doesn’t appear to be a filter or view setting to control this behavior.

Notes: I’m unsure whether this is an intentional change in v2.1.0 or a side effect of another change. If intentional, a setting to control new task insertion order would be appreciated.

This was actually an intentional change: Kanban cards in wrong order - #3 by kolaente

When tasks were added at the bottom of the stack, they would be hard to spot when more tasks were visible. Always adding them to the top makes them always discoverable in the same place.

Thank you for the response and I understand the reasoning. I am tempted to convert this to a feature request to enable/disable this behavior, because if you work in Kanbans all day long (as I do) it would be quite nice to have them “stay put” at the moment of creation.

Thank you for the speedy reply and all your hard work on this amazing project, which I rely so heavily on.