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

Configurable Behaviour for repeat tasks #2429

New Issue
Open
opened 2026-03-22 14:07:14 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-22 14:07:14 -05:00
Owner
Copy Link

Originally created by @sirlark on GitHub (Nov 25, 2025).

Description

I used to use Wunderlist/Microsoft ToDo, and really liked their repeating tasks behaviour. I know not everyone wants things to behave that way though, so I thought it would be useful to have a configurable behaviour for repeating tasks, ideally on a per project basis, otherwise per user, or global.

The options I would want are

  1. Copy on complete. If set/true, then on completion of a repeating task, make a copy of the task, including any subtasks, and mark the new main task copy uncomplete.
  2. Reset subtasks on complete. If set/true, then when completing a repeating task with subtasks, the subtasks are marked uncompleted and main task progress rest to 100%. If 'copy on complete' is also set, then the copied subtasks are marked uncompleted instead.
  3. Preserve missed tasks. If set/true, then when a repeating task's due datetime passes without being completed, a new copy of the task (and its subtasks) is created with the new due date. This implies 'copy on complete' is also set. There should also be an east way to skip missed tasks, i.e. have a button/action on the task view to either mark all but the latest copy complete, or delete all but the latest copy.

This existing issue (#898) is tangentially related regarding resetting of main task progress.

Which alternatives did you consider using instead?

No response

Originally created by @sirlark on GitHub (Nov 25, 2025). ### Description I used to use Wunderlist/Microsoft ToDo, and really liked their repeating tasks behaviour. I know not everyone wants things to behave that way though, so I thought it would be useful to have a configurable behaviour for repeating tasks, ideally on a per project basis, otherwise per user, or global. The options I would want are 1. **Copy on complete**. If set/true, then on completion of a repeating task, make a copy of the task, including any subtasks, and mark the new main task copy uncomplete. 2. **Reset subtasks on complete**. If set/true, then when completing a repeating task with subtasks, the subtasks are marked uncompleted and main task progress rest to 100%. If '_copy on complete_' is also set, then the copied subtasks are marked uncompleted instead. 3. **Preserve missed tasks**. If set/true, then when a repeating task's due datetime passes without being completed, a new copy of the task (and its subtasks) is created with the new due date. This implies '_copy on complete_' is also set. There should also be an east way to skip missed tasks, i.e. have a button/action on the task view to either mark all but the latest copy complete, or delete all but the latest copy. This existing issue (#898) is tangentially related regarding resetting of main task progress. ### Which alternatives did you consider using instead? _No response_
GiteaMirror commented 2026-03-22 14:07:15 -05:00
Author
Owner
Copy Link

@RainerEls commented on GitHub (Mar 4, 2026):

Any news on this? It's the exact functionality I'm looking for with weekly tasks that update to have a deadline of the next instance when being completed.

@RainerEls commented on GitHub (Mar 4, 2026): Any news on this? It's the exact functionality I'm looking for with weekly tasks that update to have a deadline of the next instance when being completed.
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#2429
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?