David J Patrick

Well, no, it means I was testing blindly, not entirely sure that the function was active for. :) If anything, the behavior might be extended to the other date fields;...

to be even clearer about the field or user-value in focus, maybe the prompt should not be just "Urgency coefficient:" but the rc name of the coefficient. For eample, it...

YAY! ehem.. ok then.. - values with spaces should be treated as a single item, project:'foo bar' - a terse list of udas can be generated with helper-command "_udas"

I've had a chance to start playing with the new feature (and thank you so much for implementing it) so here's some feedback; 1) after changing an urgency value, while...

In attempting to change the urgency for a field or value, for which there is no associated coefficient (eg, over ID, Description or Urg) nothing happens. It would be better...

Not all columns are visible in all reports, but in the interest of feature completeness, these column-headings should be associated with their coefficients; start = urgency.active.coefficient entry = urgency.age.coefficient depends...

.. in other words, the only logical place to set 'due', 'priority', 'project', 'tags', 'age', 'scheduled', 'uda' (implemented) 'active', 'age', 'blocked','blocking', 'waiting' (yet to be implemented) coefficients, is the top,...

That may be a task bug/oversight. I'll see what the tw devs have to say about that over IRC. as to urgency.tags.coefficient and urgency.project.coefficient, imho, they should anly be settable...

I just tried that fresh code, and it still doesn't seem possible to show/set/clear urgency.user values.. am I missing something?

urgency.user.project.word.coefficient ? (if over a project named "word") urgency.project.coefficient (if over the Project field-heading)