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

[GH-ISSUE #1478] Inconsistent filter persistence across views (Kanban, Table, List) #6410

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

Originally created by @Plong-Wasin on GitHub (Sep 11, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1478

Description

There is inconsistent behavior in how filters and query parameters are handled across different views (Kanban, Table, and List).

  • Kanban view: Filters do not generate query parameters in the URL.
  • Table view: Filters generate query parameters in the URL, but after refreshing the page, the applied filters are lost.
  • List view: Filters generate query parameters in the URL, and after refreshing the page, the filters remain correctly applied.

Expected behavior:
Filter handling should be consistent across all views. If filters are reflected in the query parameters, refreshing the page should not remove them.

Actual behavior:

  • Kanban: No query parameters at all when filters are applied.
  • Table: Query parameters appear, but filters disappear after refresh.
  • List: Works as expected — query parameters appear and filters persist after refresh.

Steps to reproduce:

  1. Open a project in Kanban view and apply filters — observe no query parameters in the URL.
  2. Switch to Table view, apply filters, and refresh the page — filters disappear.
  3. Switch to List view, apply filters, and refresh the page — filters persist as expected.

Vikunja Version

v1.0.0-rc1-141-d14443d2

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @Plong-Wasin on GitHub (Sep 11, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1478 ### Description There is inconsistent behavior in how filters and query parameters are handled across different views (Kanban, Table, and List). - **Kanban view:** Filters do not generate query parameters in the URL. - **Table view:** Filters generate query parameters in the URL, but after refreshing the page, the applied filters are lost. - **List view:** Filters generate query parameters in the URL, and after refreshing the page, the filters remain correctly applied. **Expected behavior:** Filter handling should be consistent across all views. If filters are reflected in the query parameters, refreshing the page should not remove them. **Actual behavior:** - Kanban: No query parameters at all when filters are applied. - Table: Query parameters appear, but filters disappear after refresh. - List: Works as expected — query parameters appear and filters persist after refresh. **Steps to reproduce:** 1. Open a project in Kanban view and apply filters — observe no query parameters in the URL. 2. Switch to Table view, apply filters, and refresh the page — filters disappear. 3. Switch to List view, apply filters, and refresh the page — filters persist as expected. ### Vikunja Version v1.0.0-rc1-141-d14443d2 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror added the area/filters label 2026-04-20 17:00:40 -05:00
GiteaMirror commented 2026-04-20 17:00:42 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 11, 2025):

I would have guessed this is a regression introduced by 0dee1789a2 but it seems to have been broken before as well.

<!-- gh-comment-id:3282420296 --> @kolaente commented on GitHub (Sep 11, 2025): I would have guessed this is a regression introduced by https://github.com/go-vikunja/vikunja/commit/0dee1789a274a21c1e1cadfe7bd4e5d4a901c9ca but it seems to have been broken before as well.
GiteaMirror commented 2026-04-20 17:00:42 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 11, 2025):

Fixed in https://github.com/go-vikunja/vikunja/pull/1482, please check with the next unstable build (should be ready for deployment in ~30min, also on try).

<!-- gh-comment-id:3282802304 --> @kolaente commented on GitHub (Sep 11, 2025): Fixed in https://github.com/go-vikunja/vikunja/pull/1482, please check with the next unstable build (should be ready for deployment in ~30min, also on [try](https://try.vikunja.io)).
GiteaMirror commented 2026-04-20 17:00:43 -05:00
Author
Owner
Copy Link

@Plong-Wasin commented on GitHub (Sep 12, 2025):

@kolaente It still does not work in the table view.
Here is a reproducible example on try (v1.0.0-rc1-132-d147a01c).

Should I open a new issue for this, or continue the discussion here?

<!-- gh-comment-id:3283510143 --> @Plong-Wasin commented on GitHub (Sep 12, 2025): @kolaente It still does not work in the table view. Here is a reproducible example on [try](https://try.vikunja.io/projects/1/247?filter=done+not+in+true,false&page=1) (v1.0.0-rc1-132-d147a01c). Should I open a new issue for this, or continue the discussion here?
GiteaMirror commented 2026-04-20 17:00:43 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 12, 2025):

We can continue here.

Does it work in the other views?

<!-- gh-comment-id:3283934090 --> @kolaente commented on GitHub (Sep 12, 2025): We can continue here. Does it work in the other views?
GiteaMirror commented 2026-04-20 17:00:44 -05:00
Author
Owner
Copy Link

@Plong-Wasin commented on GitHub (Sep 12, 2025):

It works correctly in the other views.

<!-- gh-comment-id:3284005005 --> @Plong-Wasin commented on GitHub (Sep 12, 2025): It works correctly in the other views.
GiteaMirror commented 2026-04-20 17:00:44 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Nov 16, 2025):

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

<!-- gh-comment-id:3538811268 --> @vikunja-bot-app[bot] commented on GitHub (Nov 16, 2025): This issue has been fixed in [`06510ea`](), 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.
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/filters
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#6410
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?