[Ml-yokadi] Priorities in ical export

[Aurélien Gâteau]

[mmm... sequanux failed to send this message]

On 03/22/10 21:33, Sébastien Renard wrote:
> Le dimanche 21 mars 2010 17:54:40, Aurélien Gâteau a écrit :
>> On 03/20/10 14:52, Sébastien Renard wrote:
>>> 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.
>
> You're right.
>
>> What about
>> this?
>> - yokadi ->  ical: set priority using your algorithm
>
> Ok.
>
>> - ical ->  yokadi: set urgency only if urgency computed from ical
>> priority differs from original yokadi urgency
>
> How could I know if it's differ ? Ical will only have 1, 2, 3...9.
>
> What we could do is to compute again urgency if task has bugs keyword
(_bug,
> _likelyhood, _severity) sets or just ignore ical urgency.

My idea was this: Apply your algorithm on the yokadi urgency. If the
result is different from the ical priority it means the user changed the
ical priority. In this case, set yokadi urgency from ical priority using
the inverse of your algorithm.

Aurélien