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 #1431] Comments showing from one task to another when visited from notification #6391

New Issue
Closed
opened 2026-04-20 16:59:22 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-20 16:59:22 -05:00
Owner
Copy Link

Originally created by @cassid4 on GitHub (Sep 7, 2025).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1431

Description

Clicking a task from a notification brings comments from task originally viewing to new task. Refreshing the page shows the correct comments.

Vikunja Version

v1.0.0-rc1

Browser and version

Chrome android

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

Wrote comment on issue 2
Image
Clicked notification and selected task 14
Image
Comment shows at the bottom of task 14 (expecting no comments on that issue)
Image

Refreshing the page resolves this display of the wrong comments

Originally created by @cassid4 on GitHub (Sep 7, 2025). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/1431 ### Description Clicking a task from a notification brings comments from task originally viewing to new task. Refreshing the page shows the correct comments. ### Vikunja Version v1.0.0-rc1 ### Browser and version Chrome android ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots Wrote comment on issue 2 <img width="1440" height="4726" alt="Image" src="https://github.com/user-attachments/assets/98023ac0-8ca5-4e12-845f-4faccb3f025d" /> Clicked notification and selected task 14 <img width="1440" height="3120" alt="Image" src="https://github.com/user-attachments/assets/474086be-5954-41e6-a376-82dd38ee487d" /> Comment shows at the bottom of task 14 (expecting no comments on that issue) <img width="1440" height="3120" alt="Image" src="https://github.com/user-attachments/assets/52ff4927-2c70-4958-b3d5-78b9d94712f3" /> Refreshing the page resolves this display of the wrong comments
GiteaMirror commented 2026-04-20 16:59:23 -05:00
Author
Owner
Copy Link

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

This has already been fixed in bb07b33dc2

You've mentioned you can't reproduce it on the demo, that means it works in unstable releases.

<!-- gh-comment-id:3263913642 --> @kolaente commented on GitHub (Sep 7, 2025): This has already been fixed in https://github.com/go-vikunja/vikunja/commit/bb07b33dc23a1216399e13ded7dd9b9e917cf2cb You've mentioned you can't reproduce it on the demo, that means it works in unstable releases.
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#6391
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?