mirror of
https://github.com/go-vikunja/vikunja.git
synced 2026-03-22 13:05:43 -05:00
Todoist migration: Buckets #218
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/vikunja#218
Reference in New Issue
Block a user
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?
Originally created by @GuyFoetz on GitHub (Apr 24, 2024).
Description
While importing some todoist projects, the Buckets are all created, but the Tasks are all put into the last created Bucket and not the corresponding bucket.
Vikunja Version
0.23.0
Browser and version
No response
Can you reproduce the bug on the Vikunja demo site?
No
Screenshots
No response
@kolaente commented on GitHub (Apr 24, 2024):
Is this still a problem in the latest unstable build?
@GuyFoetz commented on GitHub (Apr 24, 2024):
switched to unstable docker build and tried the migration again.
Result:
just 1 bucket is created, with all the tasks in it, maybe the others are automatically deleted as they are empty? as the bucket id is the same as before
@kolaente commented on GitHub (Apr 25, 2024):
This sounds like a bug. I'll take a look.
@kolaente commented on GitHub (Jun 4, 2024):
Fixed in
c17e4564e7, please check with the next unstable build (should be ready for deployment in ~45min, also on try).@GuyFoetz commented on GitHub (Oct 22, 2024):
Hi, sorry for the extreme delay.
I tested the import again (Version: v0.24.1-339-5f5d93dfa0), it works better but still get an error:
2024-10-22T10:22:42+02:00: ERROR ▶ 11a4 [creating structure] Error while creating structure: Bucket does not exist [BucketID: 12] 2024-10-22T10:22:42+02:00: ERROR ▶ 11a5 [Migration] Migration 1 from todoist for user 1 failed. Error was: Bucket does not exist [BucketID: 12]I have 2 Projects in Todoist, 1 is Imported properly with all the buckets.
The other stops importing the tasks with the error mentioned and it has 1 bucket twice what is strange.
Let me know if you need more logs :)
Regards,
Guy
@kolaente commented on GitHub (Oct 28, 2024):
Can you enable debug logging to see what happens before the error? That would help narrow it down.
@mariomaz87 commented on GitHub (Nov 3, 2024):
Should I add the variable VIKUNJA_LOG_LEVEL and set it to debug?
@kolaente commented on GitHub (Nov 3, 2024):
Yes, exactly
@mariomaz87 commented on GitHub (Nov 3, 2024):
This is the full log after launching the migration, thanks!
@tkedwards commented on GitHub (Nov 8, 2024):
I've run into the same issue, I've attached the log file showing an attempted import from Todoist with
VIKUNJA_LOG_LEVEL: debugin the Docker compose file.vikunja test.txt
@tkedwards commented on GitHub (Nov 11, 2024):
I just tried it with the latest unstable Docker build (v0.24.1-440-44c659aa34) but no luck, same errors:
@kolaente commented on GitHub (Jan 17, 2025):
I've just tried to reproduce this and was unable to. Can you add more details about what your todoist lists look like? Especially kanban boards.
@tkedwards commented on GitHub (Jan 19, 2025):
I've tested again, and I can still reproduce the same issue:
I don't use Kanban boards. I've got 4 main projects, 3 have one level of sub-projects and one has 2 levels. There are a couple of hundred tasks all up spread through the projects.
@kolaente commented on GitHub (Jan 19, 2025):
Are you using sections?
@tkedwards commented on GitHub (Jan 19, 2025):
Yes, lots of sections, spread around different projects
@kolaente commented on GitHub (Jan 20, 2025):
Since I'm still unable to reproduce this, I've added more logging in
0e37049343. Can you try it again with the next unstable build (ready in ~45min) and report back with debug logs?@tkedwards commented on GitHub (Jan 21, 2025):
Thanks, I'm away for a couple of days but will give this a try later in the week when I'm back
@tkedwards commented on GitHub (Jan 27, 2025):
Sorry for the delay:
Output of docker logs:
Not sure if that Docker unstable latest had the extra logging you added? Is there a way to get it in a docker container or would I need to build Vikunja to get that commit?
@kolaente commented on GitHub (Jan 28, 2025):
If you pull the latest
unstabledocker container, it should be fine.You'll need to enable debug logging to see the new logs though
@tkedwards commented on GitHub (Jan 30, 2025):
I think I've got the log finally, see full log file attached.
vikunja.log
@kolaente commented on GitHub (Jun 24, 2025):
Related forum thread: https://community.vikunja.io/t/incomplete-todoist-import/3763/10
@kolaente commented on GitHub (Jun 25, 2025):
Fixed in https://github.com/go-vikunja/vikunja/pull/1015, please check with the next unstable build (should be ready for deployment in ~30min, also on try).