Feature Description
The default urgencyScore formula in tasks-default.base operates at day-level granularity:
priorityWeight + max(0, 10 - daysUntilNext)
Two timed tasks at the same priority and same date score identically regardless of time of day, so a task scheduled earlier in the day and a task scheduled later in the same day tie and order non-deterministically (file iteration order).
TaskNotes supports timed scheduling fully (calendar timeGrid views, timeblocks), so the information is available. Earlier-in-day timed values are arguably more urgent than later-in-day ones at the same priority and date, since the planned slot has either passed or is closer to passing.
Proposal: add a small 0..1 boost based on the fractional day of nextDate so earlier values rank above later ones, while keeping priority and the days component dominant.
Here is a pull request that implements this: #1839
Feature Description
The default
urgencyScoreformula intasks-default.baseoperates at day-level granularity:Two timed tasks at the same priority and same date score identically regardless of time of day, so a task scheduled earlier in the day and a task scheduled later in the same day tie and order non-deterministically (file iteration order).
TaskNotes supports timed scheduling fully (calendar timeGrid views, timeblocks), so the information is available. Earlier-in-day timed values are arguably more urgent than later-in-day ones at the same priority and date, since the planned slot has either passed or is closer to passing.
Proposal: add a small 0..1 boost based on the fractional day of
nextDateso earlier values rank above later ones, while keeping priority and the days component dominant.Here is a pull request that implements this: #1839