Recurring Tasks

Recurring tasks let you automatically generate repeated copies of a task at a fixed interval — weekly standups, monthly reviews, fortnightly sprints, or any repeated activity.

Setting Up a Recurring Task

Double-click any task on the Gantt view to open the Task Editor. (Recurrence is not available for Summary Phases or Milestones.)
Scroll to the 🔁 Recurrence section near the bottom of the modal.
Tick Repeat this task automatically.
Set your repeat schedule:

Recurrence Options

Field	Description
Every	How often the task repeats. Enter a number and choose a unit: day(s), week(s), or month(s). Example: "Every 2 weeks" = fortnightly.
For N occurrences	Total number of additional copies to generate after the original. Maximum 52. Example: "For 4 occurrences" with a weekly task creates 4 more weekly copies.
Or until date	Optional end date. If set, generation stops when the next start date would exceed this date — whichever limit (count or until-date) is hit first.

Tip Leave Or until blank and just set a count. It's the simpler option for most planning scenarios.

How Instances Are Generated

When you save the task, DPlan generates sibling task rows immediately after the original in the task list:

Each instance has the same name, resources, priority, color, and notes as the original
Start dates are spaced by your chosen interval (start-to-start). Duration is preserved.
Instances start with status Not Started and progress 0%
The original task shows a 🔁 badge; generated instances show a ↺ badge
Instance rows appear slightly muted to distinguish them from hand-crafted tasks

Editing and Managing Instances

Action	How
Update progress / status on one instance	Click the bar to use the quick progress popup, or double-click to open its Task Editor
Change the recurrence pattern	Double-click the original (🔁) task, adjust the Recurrence fields, and Save — all instances are regenerated
Stop recurrence	Double-click the original, uncheck Repeat this task, and Save — all generated instances are removed
Delete one instance	Select it and use HOME → Delete Task — only that instance is removed; others are unaffected until the template is re-saved

Note Re-saving the template always removes and regenerates all instances. Any manual edits to individual instances (date changes, custom notes) will be lost on regeneration.

Example

A weekly team standup meeting:

Task:    "Weekly Standup"
Start:   2026-01-05  (Monday)
End:     2026-01-05  (1-day task)

Recurrence:
  Every 1 week(s)
  For 7 occurrences

Result: the original task on Jan 5, plus 7 copies on Jan 12, 19, 26, Feb 2, 9, 16, 23 — 8 standup tasks total, all in one go.

Tip Use recurring tasks inside a Summary Phase to group all occurrences under one collapsible phase header.