[Ml-yokadi] Priorities in ical export

[Aurélien Gâteau]

On 03/20/10 14:52, Sébastien Renard wrote:
> Le jeudi 18 mars 2010 21:07:51, David Faure a écrit :
>> So, the bug I thought I fixed at linux expo (priorities wrongly sorted
>> in korganizer) was actually not a korganizer bug, but a bug in the
>> akonadi ical export:
>> smaller numbers are supposed to be higher priority, in ical...
>
> Arg.
>
>> Sergio Martins told me:
>> "in korganizer, the highest priority is 1, and the lowest is 9"
>> and to give you this reference:
>>   http://www.ietf.org/rfc/rfc2445.txt ->  4.8.1.9 Priority
>>
>> I'll revert my korganizer change.
>>
>> I'm not sure what this means exactly for the yokadi ical export;
>> exporting 100-priority would be quite confusing (one wouldn't recognize the
>> priorities set in yokadi), but then again, exporting "-priority" might be
>> confusing too (negative numbers).
>
> Actually, yokadi lowest is -99 and highest is 100. Default is 0.
>
> We could use the following algo :
> icalPriority = - (yokadiPriority - 100) / 20
> if icalPriority>  9 : icalPriority = 9
> if icalPriority<  1 : icalPriority = 1
>
> The drawback if that a task modified in an ical too would have his priority
> rounded (0, 20, 40, 60, 80) and maximised at 80.
> I don't known if this is a major issue...

It is a problem for "bugs" tasks: the way urgency is computed from 
severity and likelihood requires fine-grained urgency values. What about 
this?
- yokadi -> ical: set priority using your algorithm
- ical -> yokadi: set urgency only if urgency computed from ical 
priority differs from original yokadi urgency

Would it work?

aurélien