Indicate 'staleness' of a next action
I have some stubborn next actions without due dates that sit in my list for ages. It would be useful to have some visual indication of 'staleness': say, if the creation date is more than 3 weeks ago, highlight the background of that action in yellow. It might actually give me enough of a kick to do the action and get it off my list.
Leave a comment
on 2005-05-28 22:25 *
By Anonymous
Status changed from Accepted to Fixed
Status changed from Accepted to Fixed
Fixed in [89].
There's a new setting in settings.yml (staleness_starts) which defines the number of days before which actions get marked as stale. Let's say you set it to 7 days. Actions created between 7 and 14 days ago get marked pale yellow, those created between 14 and 28 days ago (staleness_starts * 2) get marked darker yellow, and those created more than 28 days ago (staleness_starts * 3) are fluorescent
yellow!
There's a new setting in settings.yml (staleness_starts) which defines the number of days before which actions get marked as stale. Let's say you set it to 7 days. Actions created between 7 and 14 days ago get marked pale yellow, those created between 14 and 28 days ago (staleness_starts * 2) get marked darker yellow, and those created more than 28 days ago (staleness_starts * 3) are fluorescent
yellow!
"Images":http://www.robotii.co.uk/
Currently r92 marks everything stale regardless of the existance or non-existance of item.due date. I'm sure its quite common for people to add long-range items to their todo lists. eg. books to read by next year.
So instead of blink-blinking everything its probably better to restrict staleness checking to just items without item.due.
Note, my patch is a little messy. I need to grok the code a little more before i can start suggesting a way of refactoring/cleaning this code/logic.
So instead of blink-blinking everything its probably better to restrict staleness checking to just items without item.due.
Note, my patch is a little messy. I need to grok the code a little more before i can start suggesting a way of refactoring/cleaning this code/logic.
<a href='http://www.assembla.com/spaces/tracks-tickets/documents/aBatu80SOr3y8Pab7jnrAJ'>stale.patch</a>: Patching the staleness labelling so that it excludes items with due dates