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

[GH-ISSUE #1463] Initial filter application does not add filter query parameter to URL #6404

New Issue
Closed
opened 2026-04-20 17:00:17 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 17:00:17 -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/1463

Description

When applying a filter for the first time, the URL only includes the page=1 query parameter and does not add the filter parameter. The filter query parameter only appears after performing filtering a second time.

Example behavior:

  • Initial URL without query parameters:
    https://try.vikunja.io/projects/1/247
  • After first filter attempt:
    https://try.vikunja.io/projects/1/247?page=1 (missing filter parameter)
  • After second filter attempt:
    https://try.vikunja.io/projects/1/247?page=1&filter=done+=+true (filter parameter present)

Expected behavior:

  • Applying a filter for the first time should immediately add the corresponding filter query parameter to the URL along with the page parameter.

Steps to reproduce:

  1. Navigate to a project URL with no query parameters (e.g., https://try.vikunja.io/projects/1/247).
  2. Apply a filter (e.g., filtering by done = true).
  3. Observe that only page=1 is appended to the URL but the filter parameter is missing.
  4. Apply the filter again.
  5. Observe that now the filter parameter appears in the URL.

This inconsistent URL updating might lead to confusion or issues when sharing URLs or reloading the page with applied filters.

Vikunja Version

v1.0.0-rc1-128-e5e0413b

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/1463 ### Description When applying a filter for the first time, the URL only includes the `page=1` query parameter and does not add the filter parameter. The filter query parameter only appears after performing filtering a second time. Example behavior: - Initial URL without query parameters: `https://try.vikunja.io/projects/1/247` - After first filter attempt: `https://try.vikunja.io/projects/1/247?page=1` (missing filter parameter) - After second filter attempt: `https://try.vikunja.io/projects/1/247?page=1&filter=done+=+true` (filter parameter present) Expected behavior: - Applying a filter for the first time should immediately add the corresponding filter query parameter to the URL along with the page parameter. Steps to reproduce: 1. Navigate to a project URL with no query parameters (e.g., `https://try.vikunja.io/projects/1/247`). 2. Apply a filter (e.g., filtering by done = true). 3. Observe that only `page=1` is appended to the URL but the filter parameter is missing. 4. Apply the filter again. 5. Observe that now the filter parameter appears in the URL. This inconsistent URL updating might lead to confusion or issues when sharing URLs or reloading the page with applied filters. ### Vikunja Version v1.0.0-rc1-128-e5e0413b ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror commented 2026-04-20 17:00:18 -05:00
Author
Owner
Copy Link

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

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

<!-- gh-comment-id:3281499736 --> @kolaente commented on GitHub (Sep 11, 2025): Fixed in https://github.com/go-vikunja/vikunja/pull/1471, please check with the next unstable build (should be ready for deployment in ~30min, also on [try](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
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#6404
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?