Business, air gapped v2.2.0 here.
When I create custom properties for tasks I would like to use them as “normal” fields. That means:
- selectable in the properties for sorting or grouping a view
- addable as column in a view
- <… and other possible uses>
Example:
we use a custom property “follow-up date” for tasks. This is not the target date, but a date before in order to talk about the task in a daily, but only if the follow-up date is reached. The result is that we only talk about tasks, where someone thought that something interesting has happened (and set a follow-up date).
So, I want a view ….
- containing all tasks with a set follow-up date (the field is not mandatory)
- the follow-up date is displayed in the first view column
- the tasks are sorted by follow-up date (oldest first)
- the view is filtered by the tasks where follow-up date < @today (not possible yet, I know. So the sort does the trick)