mirror of
https://github.com/go-vikunja/vikunja.git
synced 2026-03-09 07:13:35 -05:00
Kanban does not work after importing from another Vikunja install #360
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/vikunja#360
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 @christiaangoossens on GitHub (Feb 20, 2025).
Description
Bug: Not all tasks are visible on the Kanban board after exporting a list (from one Vikunja install) and importing it into another Vikunja install. Tasks show fine on the List view every time.
Steps to reproduce
Technical details
You can see the effect in the API responses too, so it's not a frontend bug, here's an example:
Here, the first two columns have no tasks (null) and the Done column has tasks in it.
If you refresh, the output might look like this:
Even though nothing changed, suddenly only the first column includes tasks.
Reproducibility on the test server
This cannot be reproduced on the demo server, as export/import is disabled.
Vikunja Version
0.24.6
Browser and version
No response
Can you reproduce the bug on the Vikunja demo site?
No
Screenshots
No response
@kolaente commented on GitHub (Feb 21, 2025):
Can you reproduce that with an unstable build? Are you using typesense?
@christiaangoossens commented on GitHub (Feb 21, 2025):
I will try that with unstable soon and get back to you. I am using Typesense (I was not with the previous install if that matters).
@kolaente commented on GitHub (Feb 21, 2025):
Does it work without typesense?
@christiaangoossens commented on GitHub (Feb 21, 2025):
Works perfectly fine without Typesense, so that's the culprit here. Here's some logs of loading a Kanban page that I pulled before disabling Typesense:
Maybe it's not related to the import at all, but only to Typesense fallback to DB with the Kanban board?
(Also, can you check my
christiaangoossensaccount on your Git server kolaente.dev? I logged in with Github to create an issue/PR for https://kolaente.dev/vikunja/helm-chart, but I can't see any repositories when logged in. Maybe you need to approve the account manually?)@christiaangoossens commented on GitHub (Feb 21, 2025):
Additional info: Typesense has been enabled for this new instance from the start, I did not do an index because there were no tasks yet. Then, afterwards I imported the backup through the UI, so all tasks should have been indexed automatically right?
@kolaente commented on GitHub (Feb 21, 2025):
Does it work if you reindex? https://vikunja.io/docs/cli/#index
I've enabled your account.
@christiaangoossens commented on GitHub (Feb 21, 2025):
I re-enabled Typesense and the issue came back. Then first ran
vikunja index -pwith this output:And then
vikunja indexwith this output:After that it works again. Does it not run a full index when first setting up (Typesense was enabled before I added tickets in the importer)?
@christiaangoossens commented on GitHub (Feb 21, 2025):
Nevermind, the Kanban view now works with Typesense, but all other views have many missing tasks. Disabling Typesense shows everything correctly again.
@kolaente commented on GitHub (Feb 21, 2025):
No, because Vikunja has no way of knowing whether this was enabled previously. And it might take a long time to index everything, the current way allows doing this in the background and only "switching" afterwards.
Does this only happen in one specific project or in general?
@christiaangoossens commented on GitHub (Feb 21, 2025):
I would expect it to do an initial (empty) index upon first migrating the database (fully empty DB). Typesense has never been disabled for this install (until today). Should I have done an index on the empty db at the start manually?
All projects it seems, only since the index. Kanbans show correctly, but List, Table and Gantt are missing tasks.
@kolaente commented on GitHub (Feb 21, 2025):
Are they missing all tasks or only some?
@christiaangoossens commented on GitHub (Feb 21, 2025):
It seems that all list were capped to 1. Individual lists only showed 1 task, but also a filter spanning multiple lists only showed 1.
@kolaente commented on GitHub (Feb 21, 2025):
New projects as well?
Am 21. Februar 2025 19:51:21 MEZ schrieb Christiaan Goossens @.***>:
@christiaangoossens commented on GitHub (Feb 21, 2025):
Non imported? It seems to be for all of them. I turned Typesense back off already to make it usable again, so I would have to test it another time.
@hendrikreuhl commented on GitHub (Apr 10, 2025):
I'm facing the exact same issue with my instance.
I had a running instance already with typesense turned off, then installed and enabled it, run
vikunja indexand then starting the server.I'm also facing the issue that all projects kanbans are not working. It only loads one random column of the kanban with all other columns staying empty.
Standard log also outputs this:
2025-04-10T09:28:03+02:00: WARNING ▶ 120 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Could not find a field namedcomments.commentin the schema."}'. Falling back to db. 2025-04-10T09:28:03+02:00: WARNING ▶ 125 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Could not find a field namedcomments.commentin the schema."}'. Falling back to db. 2025-04-10T09:28:03+02:00: WARNING ▶ 128 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Could not find a field namedcomments.commentin the schema."}'. Falling back to db. 2025-04-10T09:28:03+02:00: WARNING ▶ 12b Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Could not find a field namedcomments.commentin the schema."}'. Falling back to db. 2025-04-10T09:28:03+02:00: WARNING ▶ 12e Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Could not find a field namedcomments.commentin the schema."}'. Falling back to db. 2025-04-10T09:28:03+02:00: WARNING ▶ 131 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Could not find a field namedcomments.commentin the schema."}'. Falling back to db. 2025-04-10T09:28:04+02:00: WARNING ▶ 160 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Could not find a field namedcomments.commentin the schema."}'. Falling back to db. 2025-04-10T09:28:04+02:00: WARNING ▶ 167 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Could not find a field namedcomments.commentin the schema."}'. Falling back to db. 2025-04-10T09:28:04+02:00: WARNING ▶ 16a Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Could not find a field namedcomments.commentin the schema."}'. Falling back to db. 2025-04-10T09:28:04+02:00: WARNING ▶ 16d Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Could not find a field namedcomments.commentin the schema."}'. Falling back to db. 2025-04-10T09:28:04+02:00: WARNING ▶ 170 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Could not find a field namedcomments.commentin the schema."}'. Falling back to db. 2025-04-10T09:28:04+02:00: WARNING ▶ 173 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Could not find a field namedcomments.commentin the schema."}'. Falling back to db.May one issue be that the
vikunja indexcommand does not index all tasks comments correctly?@kolaente commented on GitHub (Apr 10, 2025):
@hendrikreuhl it should index all comments. Not sure why it does not do that. If you do a full index, do you still see the error?