[#14032] Tasks priority range
Summary Tasks priority range
Queue Nag
Queue Version Git master
Type Enhancement
State Accepted
Priority 1. Low
Requester alex@mail.fliker09.tk
Created 2015-06-29 (2354 days ago)
Updated 2018-05-13 (1305 days ago)
Patch No

alex@mail.fliker09.tk 2015-06-29 13:27:31
You use 1-5 range and it's a problem. I am using CalDAV-Sync + Tasks 
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- 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 

Michael Rubinsky <mrubinsk@horde.org> 2015-06-29 16:14:25
I don't recall ever seeing a priority range that wide. Exchange uses 
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.

Jan Schneider <jan@horde.org> 2015-06-30 12:55:53
FWIW this RFC is younger than the priority list in Nag. Older 
iCalendar RFCs didn't specify a valid range.

ramack@raphael-mack.de 2018-04-30 09:08:46
It would be great to have this changed, as together with OpenTasks and 
Davdroid, the default priority 0 is used on creation of new tasks. 
Which finally leads to an empty PRIORITY entry in the ical...

jens.meier@nachthell.net 2018-05-13 10:09:18
I would also really appreciate if the priorities will be fixed soon, 
because the synchronisation of my tasks with davdroid is not working 
anymore since davdroid version 1.11.

Thank you very much!