Bugs around project duplication with kanban buckets

Bug
1

Looking at the demo.

Duplicating projects with a Kanband "done" bucket is broken appears fixed, but several bugs appear to remain:

  1. Create a project “test”
  2. Go to kanban view, create a second bucket “done”. Set the “Backlog” bucket as default bucket, set the “done” bucket as done bucket.
  3. Add a task in each bucket, marking the one in the done bucket as done.
  4. Duplicate the project. For easier typing, rename the clone to “test2”.
  5. BUG 1: Check the kanban view on both projects. The task that should be in the “done” bucket is gone. You can still find it in the table view, however.
  6. BUG 2: The “Backlog” bucket is not marked as default bucket in the “test2” project.
  7. From the toplevel overview, create a new task in each project using “taskx +test” and “tasky +test2”.
  8. BUG 3: Check the kanban views, again. The test2 project does not show “tasky” in the kanban view. It does show it in the table view, however.
  9. BUG 3b: In project test2, table view, mark “tasky” as done. It still does not show in any kanban column.
2

Can you reproduce this on try?

3

Yes, all of it.

One additional observation, while reproducing: If, before step 7, you mark the “Backlog” bucket in the clone as default (i.e. you do explicitly, what should have happened while cloning), bugs 3 and 3b do not trigger.

1 Like
4

Thanks for the reproduction, I’ll take a look.

5

I was able to fix the bug where the default bucket would not be set correctly in 8da1102204.

All other bugs are now fixed as well (84cbd25e67). It was caused by a default filter done = false (only show tasks which are not done) when updating the bucket.

Please check with the next unstable build (should be ready for deployment in ~45min, also on try).

2 Likes
6

I can confirm this is fixed, now. Thanks!

While at it, one corner case buglet (could arguably be a feature): When creating a new task in the a “Done” bucket, it will not be marked as done.

1 Like
7

This is now fixed in 0585045260, please check with the next unstable build (should be ready for deployment in ~45min, also on try).

2 Likes