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

Fetures request: time tracking and sublists #141

New Issue
Closed
opened 2025-11-01 20:48:34 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-01 20:48:34 -05:00
Owner
Copy Link

Originally created by @iszhi on GitHub (Jun 19, 2023).

Description

Thank you for bringing this highly effective application to the community. I greatly appreciate it. However, I would appreciate your input on two additional features that I believe would improve the application's usefulness.

Time-tracking: It would be helpful if there were a button within each task that, when clicked, starts a timer that shows how much time has elapsed below the task. This would provide better control over how much time each task takes, enable users to gauge their work efficiency, and potentially lead to improvements in productivity.

Sub-lists: Since some tasks have very similar properties but are small in scope, it would be beneficial if users could combine them into one sub-list. This would create a more manageable workspace and enhance the usability of the application.

Vikunja Frontend Version

...

Vikunja API Version

...

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

No

Screenshots

No response

Originally created by @iszhi on GitHub (Jun 19, 2023). ### Description Thank you for bringing this highly effective application to the community. I greatly appreciate it. However, I would appreciate your input on two additional features that I believe would improve the application's usefulness. Time-tracking: It would be helpful if there were a button within each task that, when clicked, starts a timer that shows how much time has elapsed below the task. This would provide better control over how much time each task takes, enable users to gauge their work efficiency, and potentially lead to improvements in productivity. Sub-lists: Since some tasks have very similar properties but are small in scope, it would be beneficial if users could combine them into one sub-list. This would create a more manageable workspace and enhance the usability of the application. ### Vikunja Frontend Version ... ### Vikunja API Version ... ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? No ### Screenshots _No response_
GiteaMirror commented 2025-11-01 20:48:36 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 20, 2023):

Thanks for the kind words! Appreate the interest.

Both of your feature requests have already been discussed in the forum here and here. Please participate in the discussion there, as the repo issue tracker is only for bug reports.

@kolaente commented on GitHub (Jun 20, 2023): Thanks for the kind words! Appreate the interest. Both of your feature requests have already been discussed in the forum [here](https://community.vikunja.io/t/feature-time-tracking/602) and [here](https://community.vikunja.io/t/nested-lists-for-better-organizined-tasks/73). Please participate in the discussion there, as the repo issue tracker is only for bug reports.
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#141
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?