Vikunja upgrade v0.24.6 to v1.0.0 error.4024 #2520

Closed
opened 2026-03-22 14:10:14 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @MarkusF42 on GitHub (Feb 6, 2026).

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

Hi,

We recently upgraded from v0.24.6 to v1.0.0 using the deb package and encountered this issue:

error.4024 The filter expression '{"filter":"done = 'false"}'' is invalid: unexpected character '{'

https://community.vikunja.io/t/problems-loading-list-tab-in-projects-filter-error/4060.

I don't really understand why this happened, as we only had those two versions on our server and this issue was not present on our test server where we tested the upgrade.
Even stranger, not all projects had this incorrect filter configuration ({ "filter": "done = false" } instead of done = false) in their list view, despite all projects being created in v0.24.6.

I have already run 'vikunja migrate', but this did not fix the issue.

Thanks in advance.

Markus

Vikunja Version

v1.0.0

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @MarkusF42 on GitHub (Feb 6, 2026). ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description Hi, We recently upgraded from v0.24.6 to v1.0.0 using the deb package and encountered this issue: `error.4024 The filter expression '{"filter":"done = 'false"}'' is invalid: unexpected character '{'` https://community.vikunja.io/t/problems-loading-list-tab-in-projects-filter-error/4060. I don't really understand why this happened, as we only had those two versions on our server and this issue was not present on our test server where we tested the upgrade. Even stranger, not all projects had this incorrect filter configuration (`{ "filter": "done = false" }` instead of `done = false`) in their list view, despite all projects being created in v0.24.6. I have already run 'vikunja migrate', but this did not fix the issue. Thanks in advance. Markus ### Vikunja Version v1.0.0 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
Author
Owner

@NixNivis commented on GitHub (Feb 23, 2026):

Possibly related to #2188 – similar view configuration migration issue. In my case, Kanban views had incompatible bucket configurations. Both issues may hint at improper migration of view configs from 0.24.6 to 1.0/1.1.

@NixNivis commented on GitHub (Feb 23, 2026): Possibly related to #2188 – similar view configuration migration issue. In my case, Kanban views had incompatible bucket configurations. Both issues may hint at improper migration of view configs from 0.24.6 to 1.0/1.1.
Author
Owner

@vikunja-bot-app[bot] commented on GitHub (Feb 24, 2026):

This issue has been fixed in #2288, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

@vikunja-bot-app[bot] commented on GitHub (Feb 24, 2026): This issue has been fixed in #2288, please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2520