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

[GH-ISSUE #116] [FEATURE] Clearing notifications #5841

New Issue
Closed
opened 2026-04-20 16:12:44 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-20 16:12:44 -05:00
Owner
Copy Link

Originally created by @valantur on GitHub (May 6, 2022).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/116

Just a feature request, definitely in the nice-to-have department: being able to either mark notifications as read either individually or all as a group so that the red dot next to the bell goes away.

I also noticed that there's no space between the name of the user and the word "assigned".

Originally created by @valantur on GitHub (May 6, 2022). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/116 Just a feature request, definitely in the nice-to-have department: being able to either mark notifications as read either individually or all as a group so that the red dot next to the bell goes away. I also noticed that there's no space between the name of the user and the word "assigned".
GiteaMirror added the enhancement label 2026-04-20 16:12:44 -05:00
GiteaMirror commented 2026-04-20 16:12:46 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (May 10, 2022):

Added to the backlog.

The spacing should be fixed in ce3f285224.

<!-- gh-comment-id:1934138603 --> @kolaente commented on GitHub (May 10, 2022): Added to the backlog. The spacing should be fixed in ce3f285224595f49e02750d620676c7af80cd6eb.
GiteaMirror commented 2026-04-20 16:12:46 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jan 22, 2025):

It has been possible for a while now to mark all notifications as read - closing this as resolved then.

<!-- gh-comment-id:2606469224 --> @kolaente commented on GitHub (Jan 22, 2025): It has been possible for a while now to mark all notifications as read - closing this as resolved then.
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 enhancement
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#5841
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?