Identify critical tasks
ubuntudroid says:
Sometimes I'm struggling identifying critical tasks, even if having prioritized them correctly. Tasks become critical, if the estimated time is long related to the time until they are due. Therefore I created this simple smart list:
(dueWithin:"1 week of today" AND timeEstimate:"> 7 hours") OR (dueWithin:"3 days of today" AND timeEstimate:"> 3 hours") OR (dueWithin:"1 day of today" AND timeEstimate:">1 hour")
This will show time critical tasks which you should start now or they will be hard to accomplish before due date. One may adapt the times I used to better values, as I assume that this is highly subjective. Nevertheless, the scheme should help you creating own criteria for identifying critical tasks.
(dueWithin:"1 week of today" AND timeEstimate:"> 7 hours") OR (dueWithin:"3 days of today" AND timeEstimate:"> 3 hours") OR (dueWithin:"1 day of today" AND timeEstimate:">1 hour")
This will show time critical tasks which you should start now or they will be hard to accomplish before due date. One may adapt the times I used to better values, as I assume that this is highly subjective. Nevertheless, the scheme should help you creating own criteria for identifying critical tasks.
ubuntudroid says:
If someone is interested: I've just updated my critical tasks smart list to use the following search:
(dueWithin:"1 week of today" AND timeEstimate:"> 7 hours") OR (dueWithin:"3 days of today" AND timeEstimate:"> 2.5 hours") OR (due:tomorow AND timeEstimate:">1 hour") OR (due:today AND timeEstimate:">0.75 hour")
This is to prevent tasks not being listed which are more than 24 hours away from now, but have less estimated time than 2.5 hours. dueWithin seems to count from the current time and not from the current day, like due:tomorrow does. So to avoid some bad suprises at the end of a day (tasks, that don't have a specific due time set, but just a due day, are automatically due at 12 pm of that day!) I decided to use due:tomorrow and due:today instead of dueWithin:"1 day of today". The value change from 3 to 2.5 hours is purely cosmetic as I found it better suites my personal taste.
(dueWithin:"1 week of today" AND timeEstimate:"> 7 hours") OR (dueWithin:"3 days of today" AND timeEstimate:"> 2.5 hours") OR (due:tomorow AND timeEstimate:">1 hour") OR (due:today AND timeEstimate:">0.75 hour")
This is to prevent tasks not being listed which are more than 24 hours away from now, but have less estimated time than 2.5 hours. dueWithin seems to count from the current time and not from the current day, like due:tomorrow does. So to avoid some bad suprises at the end of a day (tasks, that don't have a specific due time set, but just a due day, are automatically due at 12 pm of that day!) I decided to use due:tomorrow and due:today instead of dueWithin:"1 day of today". The value change from 3 to 2.5 hours is purely cosmetic as I found it better suites my personal taste.
Log in
to post a reply.