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

Saved filters render twice in sidebar on initial load #2446

New Issue
Closed
opened 2026-03-22 14:07:53 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-03-22 14:07:53 -05:00
Owner
Copy Link

Originally created by @IAMSamuelRodda on GitHub (Dec 15, 2025).

Description

Bug:

Saved filters appear in both savedFilterProjects section AND main projects list on page load. Clicking any duplicate removes it. Reappears on refresh.

Console on load:

[debug] Loading project, projectId: -4, loadedProjectId = 0, currentProject = undefined

API data is correct:

{"id": -3, "title": "@WORK", "parent_project_id": 0}
{"id": -4, "title": "@IN-PROGRESS", "parent_project_id": 0}
{"id": -5, "title": "@PERSONAL", "parent_project_id": 0}

Hypothesis:

Race condition in Navigation.vue - Sidebar renders before projectsArray populated. Computed properties (notArchivedRootProjects filtering p.id > 0) return stale data initially. Possibly triggered by data volume (22 projects, 298 tasks, 3 saved filters).

Vikunja Version

v1.0.0-rc3

Browser and version

Brave 143.1.85.111 && Firefox 146.0

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

Initial Load:

Image

After selecting each filter once:

Image
Originally created by @IAMSamuelRodda on GitHub (Dec 15, 2025). ### Description ### Bug: Saved filters appear in both `savedFilterProjects` section AND main projects list on page load. Clicking any duplicate removes it. Reappears on refresh. ### Console on load: [debug] Loading project, projectId: -4, loadedProjectId = 0, currentProject = undefined ### API data is correct: ```json {"id": -3, "title": "@WORK", "parent_project_id": 0} {"id": -4, "title": "@IN-PROGRESS", "parent_project_id": 0} {"id": -5, "title": "@PERSONAL", "parent_project_id": 0} ``` ### Hypothesis: Race condition in Navigation.vue - Sidebar renders before projectsArray populated. Computed properties (notArchivedRootProjects filtering p.id > 0) return stale data initially. Possibly triggered by data volume (22 projects, 298 tasks, 3 saved filters). ### Vikunja Version v1.0.0-rc3 ### Browser and version Brave 143.1.85.111 && Firefox 146.0 ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots ### Initial Load: <img width="389" height="817" alt="Image" src="https://github.com/user-attachments/assets/2e0cf390-70f2-43e1-8770-1b0733a84a41" /> ### After selecting each filter once: <img width="297" height="681" alt="Image" src="https://github.com/user-attachments/assets/bf53efb2-7410-4e1e-87df-393b45f4645b" />
GiteaMirror added the waiting for reply label 2026-03-22 14:07:53 -05:00
GiteaMirror commented 2026-03-22 14:07:54 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Dec 16, 2025):

If you can't reproduce it on the demo, it's likely already fixed in unstable builds. Can you try upgrading to unstable to see if it's still an issue with the latest unstable build?

@kolaente commented on GitHub (Dec 16, 2025): If you can't reproduce it on the demo, it's likely already fixed in unstable builds. Can you try upgrading to unstable to see if it's still an issue with the latest unstable build?
GiteaMirror commented 2026-03-22 14:07:54 -05:00
Author
Owner
Copy Link

@IAMSamuelRodda commented on GitHub (Dec 31, 2025):

I believe there is a comment explaining the actual source of the bug in the proposed PR solution. TLDR, Filters can be favorited via the API but not the GUI. On my install, filters were setup using the API and favorited (matching a setup I had in Todoist before migrating). This caused filters to show up in the favorites area but when clicked on, they updated the Is_Favorite to false in the browsers. Of course, upon refresh the original true status set via the api was reinstated, causing this behaviour. The fix proposed actually preserves the duplicate behaviour by helping it "persist" past the initial selection, preventing the IsFavorite false from being applied.

@IAMSamuelRodda commented on GitHub (Dec 31, 2025): I believe there is a comment explaining the actual source of the bug in the proposed PR solution. TLDR, Filters can be favorited via the API but not the GUI. On my install, filters were setup using the API and favorited (matching a setup I had in Todoist before migrating). This caused filters to show up in the favorites area but when clicked on, they updated the Is_Favorite to false in the browsers. Of course, upon refresh the original true status set via the api was reinstated, causing this behaviour. The fix proposed actually preserves the duplicate behaviour by helping it "persist" past the initial selection, preventing the IsFavorite false from being applied.
GiteaMirror commented 2026-03-22 14:07:55 -05:00
Author
Owner
Copy Link

@vikunja-bot-app[bot] commented on GitHub (Jan 6, 2026):

This issue has been fixed in #2031, 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 (Jan 6, 2026): This issue has been fixed in #2031, 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 waiting for reply
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#2446
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?