[TW-117] Ability to assign urgency coefficients to filter (a.k.a. combinations of attribute values) as well as individual attributes

_Max Muller on 2012-11-15T02:25:21Z says:_

I'm really starting to love the urgency attribute, described http://tasktools.org/gitweb/gitweb.cgi?p=rfc.git;a=blob_plain;f=rfc31-urgency.txt;hb=HEAD and elsewhere. It's awesome, As tw user/visionary David Patrick has noted, its well beyond the abilities of most all known task management programs. And it automates task management. Leave the decisions up the computer, where they belong...

However, I've encountered two types of limitations which, if they were addressed, would enhance the value of the urgency attribute much more. The first is described http://taskwarrior.org/issues/1076, and which I'd describe in the terminology of taskwarrior as follows (I hope I get this right): the ability to customize the mapping of attribute values to the numeric scale of the attribute's urgency. This would allow users to not just assign urgency coefficient to user-defined attributes, as users can do now,,, but to have urgency value differ depending on the _value_ of the user-defined attribute.

The above is a restating of a prior feature request. (again, it's this one: http://taskwarrior.org/issues/1076).

Here's the new one:

It would be even MORE flexible to be able to assign urgency not just to single attributes, but to the results of queries or filters of multiple attributes. This would make assigning urgency to a task as flexible as searching for it using taskwarrior. FOR EXAMPLE: I would like to have unscheduled tasks that are due today or tomorrow have a HIGH urgency (so I can be sure to schedule them--using tasks sched: atttribute--to a certain day or time). I would like to have have UN-scheduled tasks due today or tomorrow be much less urgent (because there's plan to do them at some time already and they don't need my attention right now).

Here how this could be implemented in a .taskrc file:

_first define a filter's urgency:__
urgency.user.filter.due-soon-and-unscheduled='(due.today or due:tomorrow) scheduled.none:'

_then assign an urgency coefficient to the filter:_
urgency.user.filter.due-soon-and-unscheduled=12.0

Having this ability would address the concern expressed here: http://taskwarrior.org/issues/1062 (although less elegantly than proposed in that feature request).It would also allow me to do something I currently can't, which is have tasks due today be very urgent and tasks due tomorrow much less urgent.