GothenburgBitFactory / GothenburgBitFactory/taskwarrior
(Un)Scheduled task urgency
- Dominant language
- C++
- Stars
- 6.1k
- Forks
- 423
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 11
Description
A scheduled task that is not yet ready can appear high in the `task next` list despite it not yet being time to work on. There does not appear to be a way to configure an urgency with a negative coefficient for this in the same way that one can for blocked tasks.
I suppose this is a feature request to somehow apply an urgency to `(+SCHEDULED and -READY)`. My current workarounds include hiding scheduled tasks by either also applying a `wait:` date, or using `task +READY` to filter them out. Removing them from the list this way is suboptimal if I still want to be cognizant that the task is coming up soon.
Contributor guide
Assessment
This issue has not been assessed yet.