-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kanban does not work after importing from another Vikunja install #412
Comments
Can you reproduce that with an unstable build? Are you using typesense? |
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). |
Does it work without typesense? |
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 |
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? |
Does it work if you reindex? https://vikunja.io/docs/cli/#index
I've enabled your account. |
I re-enabled Typesense and the issue came back. Then first ran
And then
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)? |
Nevermind, the Kanban view now works with Typesense, but all other views have many missing tasks. Disabling Typesense shows everything correctly again. |
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? |
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. |
Are they missing all tasks or only some? |
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. |
New projects as well?
Am 21. Februar 2025 19:51:21 MEZ schrieb Christiaan Goossens ***@***.***>:
…christiaangoossens left a comment (go-vikunja/vikunja#412)
> > All projects it seems, only since the index. Kanbans show correctly, but List, Table and Gantt are missing tasks.
>
> Are they missing all tasks or only some?
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.
--
Reply to this email directly or view it on GitHub:
#412 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
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. |
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
The text was updated successfully, but these errors were encountered: