Summary | Tasks priority range |
Queue | Nag |
Queue Version | Git master |
Type | Enhancement |
State | Accepted |
Priority | 1. Low |
Owners | |
Requester | alex (at) mail (dot) fliker09 (dot) tk |
Created | 06/29/2015 (3607 days ago) |
Due | |
Updated | 05/13/2018 (2558 days ago) |
Assigned | |
Resolved | |
Milestone | |
Patch | No |
because the synchronisation of my tasks with davdroid is not working
anymore since davdroid version 1.11.
Thank you very much!
Davdroid, the default priority 0 is used on creation of new tasks.
Which finally leads to an empty PRIORITY entry in the ical...
State ⇒ Accepted
iCalendar RFCs didn't specify a valid range.
Priority ⇒ 1. Low
Version ⇒ Git master
0-2, RTM uses 0-3 etc...
That being said, we should follow the standard. This will probably not
be changed until Nag 5 though, in order to avoid changing anyone's
existing priority workflow.
Priority ⇒ 2. Medium
Type ⇒ Enhancement
Summary ⇒ Tasks priority range
Queue ⇒ Nag
Milestone ⇒
Patch ⇒ No
State ⇒ New
by Marten Gajda. He uses 0-9 range. I wrote him an e-mail asking why
he uses such range. Quoting his mail:
"Actually, yes there is a very good reason to use 0-9: that's the
range specified in the iCalendar standard, see
https://tools.ietf.org/html/rfc5545#section-3.8.1.9 It says: This
priority is specified as an integer in the range 0 to 9. A value of 0
specifies an undefined priority. A value of 1 is the highest
priority. A value of 2 is the second highest priority. Subsequent
numbers specify a decreasing ordinal priority. A value of 9 is the
lowest priority. It's also the range used by most other clients and
servers."