github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-05 19:18:16 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #412] Kanban does not work after importing from another Vikunja install #6154

New Issue
Closed
opened 2026-04-20 16:45:36 -05:00 by GiteaMirror · 17 comments
GiteaMirror commented 2026-04-20 16:45:36 -05:00
Owner
Copy Link

Originally created by @christiaangoossens on GitHub (Feb 20, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/412

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

  • Create a new project
  • Fill it with tasks
  • Put the tasks in random columns on the Kanban board
  • Export all data in your Vikunja install
  • Open a new blank install
  • Import your Vikunja export from the previous install
  • Go to the same project
  • Refresh the page multiple times to see that only one column (or none) is filled with tasks and that multiple tasks are not visible, even though they all show up on the List view

Technical details

You can see the effect in the API responses too, so it's not a frontend bug, here's an example:

Image

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:

Image

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

Originally created by @christiaangoossens on GitHub (Feb 20, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/412 ### 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 - Create a new project - Fill it with tasks - Put the tasks in random columns on the Kanban board - Export all data in your Vikunja install - Open a new blank install - Import your Vikunja export from the previous install - Go to the same project - Refresh the page multiple times to see that only one column (or none) is filled with tasks and that multiple tasks are not visible, even though they all show up on the List view ### Technical details You can see the effect in the API responses too, so it's not a frontend bug, here's an example: ![Image](https://github.com/user-attachments/assets/199c4f21-1290-411c-9f07-e6ad705c367a) 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: ![Image](https://github.com/user-attachments/assets/cfe66d72-b83d-4ffe-b71d-b9f04d9ec055) 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_
GiteaMirror added the needs reproductionarea/typesense labels 2026-04-20 16:45:36 -05:00
GiteaMirror commented 2026-04-20 16:45:38 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 21, 2025):

Can you reproduce that with an unstable build? Are you using typesense?

<!-- gh-comment-id:2675017331 --> @kolaente commented on GitHub (Feb 21, 2025): Can you reproduce that with an unstable build? Are you using typesense?
GiteaMirror commented 2026-04-20 16:45:38 -05:00
Author
Owner
Copy Link

@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).

<!-- gh-comment-id:2675056213 --> @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).
GiteaMirror commented 2026-04-20 16:45:39 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 21, 2025):

Does it work without typesense?

<!-- gh-comment-id:2675060213 --> @kolaente commented on GitHub (Feb 21, 2025): Does it work without typesense?
GiteaMirror commented 2026-04-20 16:45:39 -05:00
Author
Owner
Copy Link

@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:

<time>: WARNING	▶ 1daf6 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WEB 	▶ <ip>  GET 200 /api/v1/projects/20 4.2092ms -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/projects/20/views/74/tasks?sort_by[]=position&order_by[]=asc&filter=&filter_include_nulls=false&filter_timezone=Europe%2FAmsterdam&s=&expand=subtasks&page=1 10.940063ms -<ua>
<time>: WARNING	▶ 1db0e Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WARNING	▶ 1db11 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WARNING	▶ 1db14 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WARNING	▶ 1db17 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WARNING	▶ 1db1a Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WARNING	▶ 1db1d Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WEB 	▶ <ip>  GET 200 /api/v1/projects/20/views/75/tasks?filter=&filter_include_nulls=false&s=&per_page=25&page=1 33.155676ms -<ua>
<time>: WEB 	▶ <ip>  POST 200 /api/v1/user/token 830.572µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/user 823.87µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/avatar/christiaangoossens?size=50&=1740158067874 1.071002ms -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/avatar/christiaangoossens?size=50&=1740158067890 735.783µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /projects/20/75 153.694µs -<ua>
<time>: WEB 	▶ <ip>  GET 304 /assets/index-i4VRmjeA.css 81.712µs -<ua>
<time>: WEB 	▶ <ip>  GET 304 /assets/index-BdIWn3Ve.js 153.031µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/info 75.445µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/user 850.669µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/avatar/christiaangoossens?size=50&=1740158068153 903.888µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/notifications?page=1 1.60407ms -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/projects?is_archived=true&page=1 13.857759ms -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/labels?page=1 19.103782ms -<ua>
<time>: WARNING	▶ 1db4e Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WEB 	▶ <ip>  GET 200 /api/v1/projects/20 3.761075ms -<ua>
<time>: WARNING	▶ 1db53 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WARNING	▶ 1db56 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WARNING	▶ 1db59 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WARNING	▶ 1db5c Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WARNING	▶ 1db5f Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WEB 	▶ <ip>  GET 200 /api/v1/projects/20/views/75/tasks?filter=&filter_include_nulls=false&s=&per_page=25&page=1 25.727235ms -<ua>
<time>: WEB 	▶ <ip>  GET 200 /workbox-v7.1.0/workbox-sw.js 160.009µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /workbox-v7.1.0/workbox-routing.prod.js 291.799µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /sw.js 1.241199ms -<ua>
<time>: WEB 	▶ <ip>  GET 200 /workbox-v7.1.0/workbox-core.prod.js 197.002µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /projects/20/75 164.693µs -<ua>
<time>: WEB 	▶ <ip>  GET 304 /assets/index-i4VRmjeA.css 52.874µs -<ua>
<time>: WEB 	▶ <ip>  GET 304 /assets/index-BdIWn3Ve.js 43.487µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/info 116.044µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/user 859.579µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/avatar/christiaangoossens?size=50&=1740158069006 1.018532ms -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/notifications?page=1 712.33µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/labels?page=1 6.764153ms -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/projects?is_archived=true&page=1 10.497447ms -<ua>
<time>: WARNING	▶ 1db8b Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WEB 	▶ <ip>  GET 200 /api/v1/projects/20 4.184145ms -<ua>
<time>: WARNING	▶ 1db91 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WARNING	▶ 1db94 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WARNING	▶ 1db97 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WARNING	▶ 1db9a Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WARNING	▶ 1db9d Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db.
<time>: WEB 	▶ <ip>  GET 200 /api/v1/projects/20/views/75/tasks?filter=&filter_include_nulls=false&s=&per_page=25&page=1 21.963477ms -<ua>
<time>: WEB 	▶ <ip>  GET 304 /sw.js 74.096µs -<ua>
<time>: WEB 	▶ 10.42.2.254  GET 200 /api/v1/info 142.596µs - kube-probe/1.29
<time>: WEB 	▶ 10.42.2.254  GET 200 /api/v1/info 144.822µs - kube-probe/1.29
<time>: WEB 	▶ <ip>  POST 200 /api/v1/user/token 1.049351ms -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/avatar/christiaangoossens?size=50&=1740158074957 747.509µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/user 772.531µs -<ua>
<time>: WEB 	▶ <ip>  GET 200 /api/v1/avatar/christiaangoossens?size=50&=1740158074981 661.892µs -<ua>

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 christiaangoossens account 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?)

<!-- gh-comment-id:2675126480 --> @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: ``` <time>: WARNING ▶ 1daf6 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WEB ▶ <ip> GET 200 /api/v1/projects/20 4.2092ms -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/projects/20/views/74/tasks?sort_by[]=position&order_by[]=asc&filter=&filter_include_nulls=false&filter_timezone=Europe%2FAmsterdam&s=&expand=subtasks&page=1 10.940063ms -<ua> <time>: WARNING ▶ 1db0e Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WARNING ▶ 1db11 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WARNING ▶ 1db14 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WARNING ▶ 1db17 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WARNING ▶ 1db1a Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WARNING ▶ 1db1d Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WEB ▶ <ip> GET 200 /api/v1/projects/20/views/75/tasks?filter=&filter_include_nulls=false&s=&per_page=25&page=1 33.155676ms -<ua> <time>: WEB ▶ <ip> POST 200 /api/v1/user/token 830.572µs -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/user 823.87µs -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/avatar/christiaangoossens?size=50&=1740158067874 1.071002ms -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/avatar/christiaangoossens?size=50&=1740158067890 735.783µs -<ua> <time>: WEB ▶ <ip> GET 200 /projects/20/75 153.694µs -<ua> <time>: WEB ▶ <ip> GET 304 /assets/index-i4VRmjeA.css 81.712µs -<ua> <time>: WEB ▶ <ip> GET 304 /assets/index-BdIWn3Ve.js 153.031µs -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/info 75.445µs -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/user 850.669µs -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/avatar/christiaangoossens?size=50&=1740158068153 903.888µs -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/notifications?page=1 1.60407ms -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/projects?is_archived=true&page=1 13.857759ms -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/labels?page=1 19.103782ms -<ua> <time>: WARNING ▶ 1db4e Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WEB ▶ <ip> GET 200 /api/v1/projects/20 3.761075ms -<ua> <time>: WARNING ▶ 1db53 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WARNING ▶ 1db56 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WARNING ▶ 1db59 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WARNING ▶ 1db5c Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WARNING ▶ 1db5f Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WEB ▶ <ip> GET 200 /api/v1/projects/20/views/75/tasks?filter=&filter_include_nulls=false&s=&per_page=25&page=1 25.727235ms -<ua> <time>: WEB ▶ <ip> GET 200 /workbox-v7.1.0/workbox-sw.js 160.009µs -<ua> <time>: WEB ▶ <ip> GET 200 /workbox-v7.1.0/workbox-routing.prod.js 291.799µs -<ua> <time>: WEB ▶ <ip> GET 200 /sw.js 1.241199ms -<ua> <time>: WEB ▶ <ip> GET 200 /workbox-v7.1.0/workbox-core.prod.js 197.002µs -<ua> <time>: WEB ▶ <ip> GET 200 /projects/20/75 164.693µs -<ua> <time>: WEB ▶ <ip> GET 304 /assets/index-i4VRmjeA.css 52.874µs -<ua> <time>: WEB ▶ <ip> GET 304 /assets/index-BdIWn3Ve.js 43.487µs -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/info 116.044µs -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/user 859.579µs -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/avatar/christiaangoossens?size=50&=1740158069006 1.018532ms -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/notifications?page=1 712.33µs -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/labels?page=1 6.764153ms -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/projects?is_archived=true&page=1 10.497447ms -<ua> <time>: WARNING ▶ 1db8b Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WEB ▶ <ip> GET 200 /api/v1/projects/20 4.184145ms -<ua> <time>: WARNING ▶ 1db91 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WARNING ▶ 1db94 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WARNING ▶ 1db97 Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WARNING ▶ 1db9a Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WARNING ▶ 1db9d Unable to fetch tasks from Typesense, error was 'status: 404 response: {"message": "Not found."}'. Falling back to db. <time>: WEB ▶ <ip> GET 200 /api/v1/projects/20/views/75/tasks?filter=&filter_include_nulls=false&s=&per_page=25&page=1 21.963477ms -<ua> <time>: WEB ▶ <ip> GET 304 /sw.js 74.096µs -<ua> <time>: WEB ▶ 10.42.2.254 GET 200 /api/v1/info 142.596µs - kube-probe/1.29 <time>: WEB ▶ 10.42.2.254 GET 200 /api/v1/info 144.822µs - kube-probe/1.29 <time>: WEB ▶ <ip> POST 200 /api/v1/user/token 1.049351ms -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/avatar/christiaangoossens?size=50&=1740158074957 747.509µs -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/user 772.531µs -<ua> <time>: WEB ▶ <ip> GET 200 /api/v1/avatar/christiaangoossens?size=50&=1740158074981 661.892µs -<ua> ``` 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 `christiaangoossens` account 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?)
GiteaMirror commented 2026-04-20 16:45:40 -05:00
Author
Owner
Copy Link

@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?

<!-- gh-comment-id:2675129490 --> @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?
GiteaMirror commented 2026-04-20 16:45:40 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 21, 2025):

Maybe it's not related to the import at all, but only to Typesense fallback to DB with the Kanban board?

Does it work if you reindex? https://vikunja.io/docs/cli/#index

(Also, can you check my christiaangoossens account 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?)

I've enabled your account.

<!-- gh-comment-id:2675132464 --> @kolaente commented on GitHub (Feb 21, 2025): > Maybe it's not related to the import at all, but only to Typesense fallback to DB with the Kanban board? Does it work if you reindex? https://vikunja.io/docs/cli/#index > (Also, can you check my christiaangoossens account 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?) I've enabled your account.
GiteaMirror commented 2026-04-20 16:45:41 -05:00
Author
Owner
Copy Link

@christiaangoossens commented on GitHub (Feb 21, 2025):

I re-enabled Typesense and the issue came back. Then first ran vikunja index -p with this output:

2025-02-21T17:40:54Z: INFO      ▶ 001 Using config file: /etc/vikunja/config.yml
2025-02-21T17:40:54Z: INFO      ▶ 003 Running migrations…
2025-02-21T17:40:54Z: INFO      ▶ 06b Ran all migrations successfully.
2025-02-21T17:40:54Z: INFO      ▶ 06c Indexing changed tasks… This may take a while.
2025-02-21T17:40:54Z: ERROR     ▶ 06f [Typesense Sync] No typesense sync stats yet, please run a full index via the CLI first
2025-02-21T17:40:54Z: INFO      ▶ 071 Done!

And then vikunja index with this output:

2025-02-21T17:41:01Z: INFO      ▶ 001 Using config file: /etc/vikunja/config.yml
2025-02-21T17:41:01Z: INFO      ▶ 003 Running migrations…
2025-02-21T17:41:01Z: INFO      ▶ 06b Ran all migrations successfully.
2025-02-21T17:41:01Z: INFO      ▶ 06c Indexing all tasks… This may take a while.
2025-02-21T17:41:02Z: INFO      ▶ 695 Done!

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)?

<!-- gh-comment-id:2675176517 --> @christiaangoossens commented on GitHub (Feb 21, 2025): I re-enabled Typesense and the issue came back. Then first ran `vikunja index -p` with this output: ``` 2025-02-21T17:40:54Z: INFO ▶ 001 Using config file: /etc/vikunja/config.yml 2025-02-21T17:40:54Z: INFO ▶ 003 Running migrations… 2025-02-21T17:40:54Z: INFO ▶ 06b Ran all migrations successfully. 2025-02-21T17:40:54Z: INFO ▶ 06c Indexing changed tasks… This may take a while. 2025-02-21T17:40:54Z: ERROR ▶ 06f [Typesense Sync] No typesense sync stats yet, please run a full index via the CLI first 2025-02-21T17:40:54Z: INFO ▶ 071 Done! ``` And then `vikunja index` with this output: ``` 2025-02-21T17:41:01Z: INFO ▶ 001 Using config file: /etc/vikunja/config.yml 2025-02-21T17:41:01Z: INFO ▶ 003 Running migrations… 2025-02-21T17:41:01Z: INFO ▶ 06b Ran all migrations successfully. 2025-02-21T17:41:01Z: INFO ▶ 06c Indexing all tasks… This may take a while. 2025-02-21T17:41:02Z: INFO ▶ 695 Done! ``` 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)?
GiteaMirror commented 2026-04-20 16:45:42 -05:00
Author
Owner
Copy Link

@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.

<!-- gh-comment-id:2675195217 --> @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.
GiteaMirror commented 2026-04-20 16:45:42 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 21, 2025):

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)?

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.

Nevermind, the Kanban view now works with Typesense, but all other views have many missing tasks. Disabling Typesense shows everything correctly again.

Does this only happen in one specific project or in general?

<!-- gh-comment-id:2675280762 --> @kolaente commented on GitHub (Feb 21, 2025): > 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)? 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. > Nevermind, the Kanban view now works with Typesense, but all other views have many missing tasks. Disabling Typesense shows everything correctly again. Does this only happen in one specific project or in general?
GiteaMirror commented 2026-04-20 16:45:43 -05:00
Author
Owner
Copy Link

@christiaangoossens 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.

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?

Does this only happen in one specific project or in general?

All projects it seems, only since the index. Kanbans show correctly, but List, Table and Gantt are missing tasks.

<!-- gh-comment-id:2675285006 --> @christiaangoossens 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. 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? > Does this only happen in one specific project or in general? All projects it seems, only since the index. Kanbans show correctly, but List, Table and Gantt are missing tasks.
GiteaMirror commented 2026-04-20 16:45:44 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 21, 2025):

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?

<!-- gh-comment-id:2675297542 --> @kolaente commented on GitHub (Feb 21, 2025): > 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?
GiteaMirror commented 2026-04-20 16:45:45 -05:00
Author
Owner
Copy Link

@christiaangoossens commented on GitHub (Feb 21, 2025):

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.

<!-- gh-comment-id:2675304233 --> @christiaangoossens commented on GitHub (Feb 21, 2025): > > 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.
GiteaMirror commented 2026-04-20 16:45:45 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Feb 21, 2025):

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:
https://github.com/go-vikunja/vikunja/issues/412#issuecomment-2675304233
You are receiving this because you commented.

Message ID: @.***>

<!-- gh-comment-id:2675307134 --> @kolaente commented on GitHub (Feb 21, 2025): 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: >https://github.com/go-vikunja/vikunja/issues/412#issuecomment-2675304233 >You are receiving this because you commented. > >Message ID: ***@***.***>
GiteaMirror commented 2026-04-20 16:45:45 -05:00
Author
Owner
Copy Link

@christiaangoossens commented on GitHub (Feb 21, 2025):

New projects as well?

Am 21. Februar 2025 19:51:21 MEZ schrieb Christiaan Goossens @.***>:
…

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.

<!-- gh-comment-id:2675310616 --> @christiaangoossens commented on GitHub (Feb 21, 2025): > New projects as well? > > Am 21. Februar 2025 19:51:21 MEZ schrieb Christiaan Goossens ***@***.***>: > […](#) 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.
GiteaMirror commented 2026-04-20 16:45:46 -05:00
Author
Owner
Copy Link

@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 index and 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 named comments.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.comment in the schema."}'. Falling back to db.

May one issue be that the vikunja index command does not index all tasks comments correctly?

<!-- gh-comment-id:2791840081 --> @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 index` and 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 named `comments.comment` in 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 named `comments.comment` in 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 named `comments.comment` in 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 named `comments.comment` in 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 named `comments.comment` in 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 named `comments.comment` in 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 named `comments.comment` in 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 named `comments.comment` in 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 named `comments.comment` in 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 named `comments.comment` in 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 named `comments.comment` in 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 named `comments.comment` in the schema."}'. Falling back to db.` May one issue be that the `vikunja index` command does not index all tasks comments correctly?
GiteaMirror commented 2026-04-20 16:45:46 -05:00
Author
Owner
Copy Link

@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?

<!-- gh-comment-id:2792095412 --> @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?
GiteaMirror commented 2026-04-20 16:45:47 -05:00
Author
Owner
Copy Link

@tink-bot commented on GitHub (Mar 3, 2026):

Closing as Typesense support has been removed in Vikunja v2.0.0. See https://vikunja.io/changelog/vikunja-v2.0.0-was-released/#breaking-change-typesense-removal

<!-- gh-comment-id:3989912609 --> @tink-bot commented on GitHub (Mar 3, 2026): Closing as Typesense support has been removed in Vikunja v2.0.0. See https://vikunja.io/changelog/vikunja-v2.0.0-was-released/#breaking-change-typesense-removal
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label area/typesense needs reproduction
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#6154
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?