Skip to content

Commit 7056c18

Browse files
committed
docs: Expand on priority of date fields in 'Recurring Tasks.md'
1 parent b2353ec commit 7056c18

File tree

1 file changed

+16
-4
lines changed

1 file changed

+16
-4
lines changed

docs/Getting Started/Recurring Tasks.md

Lines changed: 16 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -192,13 +192,25 @@ This is intentional. As well as matching what the user requested, it matches the
192192
## Priority of Dates
193193

194194
A task can have [[Dates|various dates]].
195+
195196
When a task has multiple dates, one of them is selected as reference date based on the following priorities:
196197

197-
1. Due date
198-
2. Scheduled date
199-
3. Start date
198+
> [!Info] Priority of date fields, with default settings
199+
>
200+
> 1. **Due** date
201+
> 2. **Scheduled** date
202+
> 3. **Start** date
200203
201-
> If the "Remove scheduled date on recurrence" setting is true, the Start Date will be chosen before the Scheduled date.
204+
> [!Info] Priority of date fields if 'Remove scheduled date on recurrence' is enabled
205+
> When the [[#Remove scheduled date on recurrence]] setting is enabled, the Start date is prioritized over the Scheduled date because the Scheduled date will be removed from the next occurrence.
206+
>
207+
> 1. **Due** date
208+
> 2. **Start** date
209+
> 3. **Scheduled** date
210+
>
211+
> It makes more sense to calculate the next occurrence based on a date that will actually exist in the new task.
212+
>
213+
> The Start date provides a more stable reference for calculating future recurrences, especially since you'll typically add a new Scheduled date later when you're ready to work on the task.
202214
203215
If more dates than the reference date exist on the original recurring task, the next occurrence will have the same dates.
204216
All dates of the next occurring task will have the relative distance to the reference date that they had on the original task.

0 commit comments

Comments
 (0)