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

Finishing a task should set the progress to 100% #2271

New Issue
Open
opened 2026-03-22 13:59:58 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-03-22 13:59:58 -05:00
Owner
Copy Link

Originally created by @mawoka-myblock on GitHub (Aug 13, 2025).

Description

When I finish a task, I'm probably done and thus have completed 100% of it. What I would wish:

  • Dismiss the progress percentage
  • Set the percentage to 100%

One of these seem more logical to me than having a finished task at 60%.

Thanks a lot for this awesome application!

Vikunja Version

0.24.6

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

No response

Originally created by @mawoka-myblock on GitHub (Aug 13, 2025). ### Description When I finish a task, I'm probably done and thus have completed 100% of it. What I would wish: - Dismiss the progress percentage - Set the percentage to 100% One of these seem more logical to me than having a finished task at 60%. Thanks a lot for this awesome application! ### Vikunja Version 0.24.6 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots _No response_
GiteaMirror commented 2026-03-22 13:59:59 -05:00
Author
Owner
Copy Link

@nsmith31415 commented on GitHub (Sep 22, 2025):

Bumping this - I would like to see this feature as well

@nsmith31415 commented on GitHub (Sep 22, 2025): Bumping this - I would like to see this feature as well
GiteaMirror commented 2026-03-22 13:59:59 -05:00
Author
Owner
Copy Link

@mawoka-myblock commented on GitHub (Sep 22, 2025):

The other way around could also be an option: setting the progress to 100% could mark the task as finished.

@mawoka-myblock commented on GitHub (Sep 22, 2025): The other way around could also be an option: setting the progress to 100% could mark the task as finished.
GiteaMirror commented 2026-03-22 14:00:00 -05:00
Author
Owner
Copy Link

@nsmith31415 commented on GitHub (Sep 22, 2025):

I'm less sold on that, because you could have a task at 100% and still be reviewing it/verifying it. Like all the work is done but you're just making sure it all works as expected before you mark it "complete"/"done".

I would love configuration options for both, though!

@nsmith31415 commented on GitHub (Sep 22, 2025): I'm less sold on that, because you could have a task at 100% and still be reviewing it/verifying it. Like all the work is done but you're just making sure it all works as expected before you mark it "complete"/"done". I would love configuration options for both, though!
GiteaMirror commented 2026-03-22 14:00:01 -05:00
Author
Owner
Copy Link

@adan-ea commented on GitHub (Dec 23, 2025):

Hi there!
Maybe an idea that could add to this idea is to base the percentage on the sub tasks completion status!
Or if we want to be more complex it could even be done based on the percentage completion of each sub task.
I thought about it (not that long so it could be improved) and here is an example:

Main task progress: 47.5%

  • Sub task 1
  • Sub task 3 progress: 50%
  • Sub task 4 progress: 80%
  • Sub task 5
  • Sub task 7 progress: 50%
  • Sub task 8
  • Sub task 2
  • Sub task 6

Calculation:
Total sub-tasks: 8
Sub tasks: [0, 100, 50, 80, 0, 100, 50, 0]
main_progress = (0 + 100 + 50 + 80 + 0 + 100 + 50 + 0) / 8
main_progress = 47.5%

So the rule would basically be:
main_progress = sum(sub_task_progress) / total_sub_tasks

@adan-ea commented on GitHub (Dec 23, 2025): Hi there! Maybe an idea that could add to this idea is to base the percentage on the sub tasks completion status! Or if we want to be more complex it could even be done based on the percentage completion of each sub task. I thought about it (not that long so it could be improved) and here is an example: Main task `progress:` 47.5% - [ ] Sub task 1 - [ ] Sub task 3 `progress:` 50% - [ ] Sub task 4 `progress:` 80% - [ ] Sub task 5 - [ ] Sub task 7 `progress:` 50% - [ ] Sub task 8 - [x] Sub task 2 - [x] Sub task 6 Calculation: Total sub-tasks: 8 Sub tasks: [0, 100, 50, 80, 0, 100, 50, 0] main_progress = (0 + 100 + 50 + 80 + 0 + 100 + 50 + 0) / 8 main_progress = 47.5% So the rule would basically be: `main_progress = sum(sub_task_progress) / total_sub_tasks`
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#2271
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?