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

Unable to mark a single notification as read #2204

New Issue
Open
opened 2026-03-22 13:57:19 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-22 13:57:19 -05:00
Owner
Copy Link

Originally created by @vikunja-bot on GitHub (Apr 1, 2025).

Original issue by tcassaert on 2025-01-20T08:13:59.000Z

Description

I'm trying to build something to send my notifications in Vikunja to Gotify. For that, I'd like to be able to mark a notification as read when the message is sent to Gotify.

When trying that, it seems impossible to mark just 1 notification as read. The Mark all as read works as expected.

When looking into the code, I didn't really find any implementation of this functionality, but it is in the Swagger API docs, so maybe I'm just not looking at the right place or not for the right thing.

Vikunja Version

v0.24.1-694-5c31ccaddd

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Original issue on Gitea

Originally created by @vikunja-bot on GitHub (Apr 1, 2025). _Original issue by tcassaert on 2025-01-20T08:13:59.000Z_ ### Description I'm trying to build something to send my notifications in Vikunja to Gotify. For that, I'd like to be able to mark a notification as read when the message is sent to Gotify. When trying that, it seems impossible to mark just 1 notification as read. The `Mark all as read` works as expected. When looking into the code, I didn't really find any implementation of this functionality, but it is in the Swagger API docs, so maybe I'm just not looking at the right place or not for the right thing. ### Vikunja Version v0.24.1-694-5c31ccaddd ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_ [Original issue on Gitea](https://kolaente.dev/vikunja/vikunja/issues/3033)
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#2204
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?