Saved filters are not updated when tasks are updated #219

Closed
opened 2025-11-01 20:51:13 -05:00 by GiteaMirror · 6 comments
Owner

Originally created by @mvalois on GitHub (Apr 25, 2024).

Description

When creating a saved filter to get tasks for a given user, shown tasks are not updated until we edit their description. For instance, when removing the assignee from the task, it still appears in the list of the saved filter.

Vikunja Version

0.22.1

Browser and version

Firefox last version, reproducible using debian desktop client

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @mvalois on GitHub (Apr 25, 2024). ### Description When creating a saved filter to get tasks for a given user, shown tasks are not updated until we edit their description. For instance, when removing the assignee from the task, it still appears in the list of the saved filter. ### Vikunja Version 0.22.1 ### Browser and version Firefox last version, reproducible using debian desktop client ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror added the bug label 2025-11-01 20:51:13 -05:00
Author
Owner

@kolaente commented on GitHub (Apr 25, 2024):

Please upgrade your instance to 0.23.0 or the last unstable build. 0.22.1 is not supported anymore.

@kolaente commented on GitHub (Apr 25, 2024): Please upgrade your instance to 0.23.0 or the last unstable build. 0.22.1 is not supported anymore.
Author
Owner

@mvalois commented on GitHub (Apr 25, 2024):

Even after upgrading both the server and client to 0.23.0 the issue still appears.

@mvalois commented on GitHub (Apr 25, 2024): Even after upgrading both the server and client to 0.23.0 the issue still appears.
Author
Owner

@kolaente commented on GitHub (Apr 26, 2024):

Does it work with the latest unstable build? (make a backup before upgrading!) Are you using Typesense?

@kolaente commented on GitHub (Apr 26, 2024): Does it work with the latest unstable build? (make a backup before upgrading!) Are you using Typesense?
Author
Owner

@mvalois commented on GitHub (Apr 28, 2024):

yes we are using typesense.

@mvalois commented on GitHub (Apr 28, 2024): yes we are using typesense.
Author
Owner

@mvalois commented on GitHub (Jun 4, 2024):

Disabling typesense resolves the issue.

@mvalois commented on GitHub (Jun 4, 2024): Disabling typesense resolves the issue.
Author
Owner

@kolaente commented on GitHub (Jun 5, 2024):

This should be fixed in f131289d32, please check with the next unstable build (should be ready for deployment in ~45min).

You'll need to do a full reindex via the vikunja index cli command.

@kolaente commented on GitHub (Jun 5, 2024): This should be fixed in https://github.com/go-vikunja/vikunja/commit/f131289d326516268f6d647468434b7d52c50f58, please check with the next unstable build (should be ready for deployment in ~45min). You'll need to do a full reindex via the `vikunja index` cli command.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#219