Marty Oehme
7973b606b9
Up to now tasks that were blocking other tasks would just get a bump in urgency in taskwarrior. Vice versa for tasks being blocked. However, this could still lead to situations in which a task A blocking task B would appear in the list (sorted by urgency) BEHIND task B. If one task is blocking another, I can not reasonably assume to be able to complete the one blocked, right? So this lead to more confusion that anything and now, any task that blocks another task simply inherits its urgency, appearing directly before the other task in the list. Should solve the problem, though they may not be able to receive their own urgencies anymore, should that be important. |
||
---|---|---|
.. | ||
.config | ||
.local |