You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Getting Started/Statuses.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ Here is some more detail.
61
61
-**Next Status Symbol**
62
62
- the status symbol to use when the task is toggled.
63
63
-**Status Type**
64
-
- one of `TODO`, `IN_PROGRESS`, `DONE`, `CANCELLED`, `NON_TASK`.
64
+
- one of `TODO`, `IN_PROGRESS`, `ON_HOLD`, `DONE`, `CANCELLED`, `NON_TASK`.
65
65
- Tasks needs to know the type of each status, so that it knows how to treat them when searching, and what to do when tasks with the status are toggled.
66
66
- types are searchable with `status.type`, for example `status.type is IN_PROGRESS`.
Copy file name to clipboardExpand all lines: docs/Getting Started/Statuses/Status Types.md
+32-20Lines changed: 32 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,10 +15,11 @@ With the new ability to create a variety of [[Custom Statuses]], Tasks needs to
15
15
- how to treat tasks when searching,
16
16
- and what to do when tasks with the status are toggled, both for adding or removing Done dates, and for creating new task recurrences.
17
17
18
-
This was solved by the introduction of 'Status Types', which are simply a set of 5 possible types of status:
18
+
This was solved by the introduction of 'Status Types', which are simply a set of 6 possible types of status:
19
19
20
20
-`TODO`
21
21
-`IN_PROGRESS`
22
+
-`ON_HOLD`
22
23
-`DONE`
23
24
-`CANCELLED`
24
25
-`NON_TASK`
@@ -33,6 +34,13 @@ Self explanatory, we hope: this can be thought of as 'things not yet started'.
33
34
34
35
Use of this is totally optional. You may find it useful to be able to prioritise completing tasks which have already been started.
35
36
37
+
### ON_HOLD
38
+
39
+
> [!released]
40
+
> The `ON_HOLD` Status Type was introduced in Tasks X.Y.Z.
41
+
42
+
Use this for tasks you've decided are currently unworkable—for example, when awaiting external input or any circumstances you cannot control, such as feedback, decisions, or third-party actions. Unlike [[Priority|priorities]], which help you choose what to work on, or [[Task Dependencies|dependencies]], which enforce sequencing, `ON_HOLD` signals that a task is simply not actionable right now.
43
+
36
44
### DONE
37
45
38
46
The `DONE` type is used to determine:
@@ -71,14 +79,16 @@ The `status.type` filter uses a new pattern in the Tasks code which some refer t
71
79
72
80
If Tasks does not understand a `status.type` instruction, it reports this kind of message:
Tasks query: Invalid status.type instruction: 'status.type in progress'.
76
85
Allowed options: 'is' and 'is not' (without quotes).
77
-
Allowed values: TODO DONE IN_PROGRESS CANCELLED NON_TASK
86
+
Allowed values: TODO DONE IN_PROGRESS ON_HOLD CANCELLED NON_TASK
78
87
Note: values are case-insensitive,
79
88
so 'in_progress' works too, for example.
80
89
Example: status.type is not NON_TASK
81
90
```
91
+
<!-- endSnippet -->
82
92
83
93
### Status Types in Tasks filters
84
94
@@ -89,26 +99,28 @@ For example, how are they used by the old `done` and `not done` filters?
89
99
If you are interested in detail, this table demonstrates the behaviour of each of the status types in Tasks.
90
100
Each column shows a representative example task with the given status type.
91
101
92
-
The tasks shown are purely examples for context. The`~` column is just an arbitrary example to show `NON_TASK`'s behaviour'. You can assign each of these types to any of your custom statuses.
102
+
The tasks shown are purely examples for context. For example, the`~` column is just an arbitrary example to show `NON_TASK`'s behaviour'. You can assign each of these types to any of your custom statuses.
93
103
94
104
<!-- placeholder to force blank line before included text --><!-- include: DocsSamplesForStatuses.test.Status_Transitions_status-types.approved.md -->
95
105
96
-
| Operation and status.type | TODO | IN_PROGRESS | DONE | CANCELLED | NON_TASK |
Copy file name to clipboardExpand all lines: docs/Queries/Sorting.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,7 @@ sort by function !task.isDone
86
86
```
87
87
88
88
- `sort by function` sorts `true` before `false`
89
-
- Hence, we use `!` to negate `task.isDone`, so tasks with [[Status Types|Status Type]] `TODO`and `IN_PROGRESS` tasks are sorted **before** `DONE`, `CANCELLED` and `NON_TASK`.
89
+
- Hence, we use `!` to negate `task.isDone`, so tasks with [[Status Types|Status Type]] `TODO`, `IN_PROGRESS` and `ON_HOLD` tasks are sorted **before** `DONE`, `CANCELLED` and `NON_TASK`.
90
90
91
91
<!-- placeholder to force blank line after included text --><!-- endInclude -->
Copy file name to clipboardExpand all lines: docs/Quick Reference.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ This table summarizes the filters and other options available inside a `tasks` b
15
15
|**[[Filters#Filters for Dates in Tasks\|Status]]**|||||
16
16
|`done`<br>`not done`|`sort by status`|`group by status`||`task.isDone`|
17
17
|`status.name (includes, does not include) <string>`<br>`status.name (regex matches, regex does not match) /regex/i`|`sort by status.name`|`group by status.name`||`task.status.name`|
18
-
|`status.type (is, is not) (TODO, DONE, IN_PROGRESS, CANCELLED, NON_TASK)`|`sort by status.type`|`group by status.type`||`task.status.type`<br>`task.status.typeGroupText`|
18
+
|`status.type (is, is not) (TODO, DONE, IN_PROGRESS, ON_HOLD, CANCELLED, NON_TASK)`|`sort by status.type`|`group by status.type`||`task.status.type`<br>`task.status.typeGroupText`|
- Add [[Status Types#ON_HOLD|ON_HOLD]] status type.
16
17
- Add 'Copy results' button: an initial implementation, which is not yet documented.
17
18
- 7.22.0:
18
19
- Fix [[Recurring Tasks#Priority of Dates|priority of dates in recurring tasks]] when using [[Recurring Tasks#Remove scheduled date on recurrence|Remove scheduled date on recurrence]].
0 commit comments