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

Comment preview in task card #2389

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

Originally created by @xeruf on GitHub (Oct 16, 2025).

Description

As we are using Vikunja as primary project management and cutting out duplicating the work updates on another tool, one small lacking feature has become apparent: The ability to see whether a task has comments.

Github has these nice little icons on issues, and they would really help:

Image

Because for me I would like to see at a glance:
Where did something change, is there a question in a comment on a task I should respond to?
Ideally this could include unread tracking - if you haven't opened a task since the last comment was made, there could be a blue dot in this notification bubble.

This should be available in all views: Table, List, Kanban

Which alternatives did you consider using instead?

clicking at each task to see if there's something new urgh
or writing an update in our chat tool saying: "please check task xy" - which is really the kind of overhead we want to eliminate ;)

Originally created by @xeruf on GitHub (Oct 16, 2025). ### Description As we are using Vikunja as primary project management and cutting out duplicating the work updates on another tool, one small lacking feature has become apparent: The ability to see whether a task has comments. Github has these nice little icons on issues, and they would really help: <img width="90" height="216" alt="Image" src="https://github.com/user-attachments/assets/cb4965c8-bea1-4498-92ea-5fc9825e3bcc" /> Because for me I would like to see at a glance: Where did something change, is there a question in a comment on a task I should respond to? Ideally this could include unread tracking - if you haven't opened a task since the last comment was made, there could be a blue dot in this notification bubble. This should be available in all views: Table, List, Kanban ### Which alternatives did you consider using instead? clicking at each task to see if there's something new urgh or writing an update in our chat tool saying: "please check task xy" - which is really the kind of overhead we want to eliminate ;)
GiteaMirror commented 2026-03-22 14:05:32 -05:00
Author
Owner
Copy Link

@NeptunedGmbH commented on GitHub (Oct 16, 2025):

+1

@NeptunedGmbH commented on GitHub (Oct 16, 2025): +1
GiteaMirror commented 2026-03-22 14:05:32 -05:00
Author
Owner
Copy Link

@mithileshgupta12 commented on GitHub (Nov 1, 2025):

Hi! I'd like to work on this feature. My plan is to:

  • Add a comment count indicator to task cards across Kanban, List, and Table views
  • Include unread tracking (visual indicator for tasks with new comments since last viewed)

Before I start, any guidance on:

  • Existing patterns for tracking "last viewed" on tasks?
  • Preferred icon/badge placement and styling?

Happy to discuss the approach further!

@mithileshgupta12 commented on GitHub (Nov 1, 2025): Hi! I'd like to work on this feature. My plan is to: - Add a comment count indicator to task cards across Kanban, List, and Table views - Include unread tracking (visual indicator for tasks with new comments since last viewed) Before I start, any guidance on: - Existing patterns for tracking "last viewed" on tasks? - Preferred icon/badge placement and styling? Happy to discuss the approach further!
GiteaMirror commented 2026-03-22 14:05:32 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 2, 2025):

@mithileshgupta12 great!

I would split this in two PRs:

  1. Comment count:
    • In the api, use an expand query on /tasks endpoints (look at how this is done for subtasks) to make comment count optional
    • Check if db indexes to make this fast exist
    • Once the api can optionally return the comments count, adjust the frontend to include the parameter when querying and show it
    • For styling, I would look at the "this task has a description" icon and what GitHub is doing and then do something similar
  2. Unread tracking:
    • In the api, this should be a new endpoint to have more control over when a task is marked as read. Since it is an action that has side-effects, it should not happen as part of the GET request that happens when fetching the task.
    • We'll need to see how/if this interacts with marking notifications as read, maybe we can even reuse the existing notification things?
@kolaente commented on GitHub (Nov 2, 2025): @mithileshgupta12 great! I would split this in two PRs: 1. Comment count: * In the api, use an `expand` query on `/tasks` endpoints (look at how this is done for subtasks) to make comment count optional * Check if db indexes to make this fast exist * Once the api can optionally return the comments count, adjust the frontend to include the parameter when querying and show it * For styling, I would look at the "this task has a description" icon and what GitHub is doing and then do something similar 2. Unread tracking: * In the api, this should be a new endpoint to have more control over when a task is marked as read. Since it is an action that has side-effects, it should not happen as part of the GET request that happens when fetching the task. * We'll need to see how/if this interacts with marking notifications as read, maybe we can even reuse the existing notification things?
GiteaMirror commented 2026-03-22 14:05:33 -05:00
Author
Owner
Copy Link

@mithileshgupta12 commented on GitHub (Nov 3, 2025):

Ok got it. I'll work on this

@mithileshgupta12 commented on GitHub (Nov 3, 2025): Ok got it. I'll work on this
GiteaMirror commented 2026-03-22 14:05:33 -05:00
Author
Owner
Copy Link

@mithileshgupta12 commented on GitHub (Nov 8, 2025):

I added the pr for the first task

https://github.com/go-vikunja/vikunja/pull/1771

@mithileshgupta12 commented on GitHub (Nov 8, 2025): I added the pr for the first task https://github.com/go-vikunja/vikunja/pull/1771
GiteaMirror commented 2026-03-22 14:05:34 -05:00
Author
Owner
Copy Link

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

https://github.com/go-vikunja/vikunja/pull/1771 has been merged, we now have comment count on tasks.

@kolaente commented on GitHub (Nov 11, 2025): https://github.com/go-vikunja/vikunja/pull/1771 has been merged, we now have comment count on tasks.
GiteaMirror commented 2026-03-22 14:05:34 -05:00
Author
Owner
Copy Link

@mithileshgupta12 commented on GitHub (Nov 17, 2025):

@kolaente

For unread tracking, should we mark tasks as read:

  1. When opening the task (mark entire task as read at once)
  2. When viewing individual comments (track each comment separately, like GitHub)
  3. Or maybe have a button to mark as read?

Which approach would you prefer?

@mithileshgupta12 commented on GitHub (Nov 17, 2025): @kolaente For unread tracking, should we mark tasks as read: 1. **When opening the task** (mark entire task as read at once) 2. **When viewing individual comments** (track each comment separately, like GitHub) 3. **Or maybe have a button to mark as read?** Which approach would you prefer?
GiteaMirror commented 2026-03-22 14:05:35 -05:00
Author
Owner
Copy Link

@xeruf commented on GitHub (Nov 17, 2025):

I think when opening the task is enough, everything else will introduce unneccesary overhead

@xeruf commented on GitHub (Nov 17, 2025): I think when opening the task is enough, everything else will introduce unneccesary overhead
GiteaMirror commented 2026-03-22 14:05:35 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 17, 2025):

What @xeruf said

@kolaente commented on GitHub (Nov 17, 2025): What @xeruf said
GiteaMirror commented 2026-03-22 14:05:36 -05:00
Author
Owner
Copy Link

@mithileshgupta12 commented on GitHub (Nov 21, 2025):

I added pr for the second task

https://github.com/go-vikunja/vikunja/pull/1857

@mithileshgupta12 commented on GitHub (Nov 21, 2025): I added pr for the second task https://github.com/go-vikunja/vikunja/pull/1857
GiteaMirror commented 2026-03-22 14:05:36 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 27, 2025):

With https://github.com/go-vikunja/vikunja/pull/1857 merged, this is now fully implemented. Thanks a bunch to @mithileshgupta12 for implementing this!

Please check with the next unstable build (should be ready for deployment in ~30min, also on try).

@kolaente commented on GitHub (Nov 27, 2025): With https://github.com/go-vikunja/vikunja/pull/1857 merged, this is now fully implemented. Thanks a bunch to @mithileshgupta12 for implementing this! Please check with the next unstable build (should be ready for deployment in ~30min, also on [try](https://try.vikunja.io)).
GiteaMirror commented 2026-03-22 14:05:37 -05:00
Author
Owner
Copy Link

@mithileshgupta12 commented on GitHub (Nov 27, 2025):

Thanks for merging this @kolaente! I enjoyed working on this. If there are other issues you'd like help with, I'd be glad to take them on.

@mithileshgupta12 commented on GitHub (Nov 27, 2025): Thanks for merging this @kolaente! I enjoyed working on this. If there are other issues you'd like help with, I'd be glad to take them on.
GiteaMirror commented 2026-03-22 14:05:37 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 27, 2025):

The things I'm concerned with right now are mostly bugs - the kind of bugs that are hard to reproduce 🙃 if you want to have a crack at them, please check out these issues.

@kolaente commented on GitHub (Nov 27, 2025): The things I'm concerned with right now are mostly bugs - the kind of bugs that are hard to reproduce 🙃 if you want to have a crack at them, please [check out these issues](https://github.com/go-vikunja/vikunja/issues?q=is%3Aissue%20state%3Aopen%20type%3ABug%20-label%3A%22waiting%20for%20reply%22%20-label%3Aarea%2Ftypesense%20-label%3A%22upstream%20issue%22%20-label%3Aarea%2Fcaldav).
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#2389
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?