Tickets :: [#11694] Priority offset with SyncML / Nag

Summary	Priority offset with SyncML / Nag
Queue	Synchronization
Queue Version	Git master
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	horde (at) luetgens (dot) org
Created	11/13/2012 (4620 days ago)
Due
Updated	11/14/2012 (4619 days ago)
Assigned
Resolved	11/14/2012 (4619 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

11/14/2012 06:16:28 PM	Jan Schneider	Comment #2 State ⇒ Not A Bug	Reply to this comment
There is no defined scale for priorities. Every client makes up it's own scale. We try to map as good as we can.

11/13/2012 08:13:19 AM	horde (at) luetgens (dot) org	Comment #1 State ⇒ Unconfirmed Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Priority offset with SyncML / Nag Queue ⇒ Synchronization Milestone ⇒ Patch ⇒ No	Reply to this comment
When synchronizing Tasks via SyncML, the priority is wrong. "High" priority on the synchronized device is "3" in Nag, "Normal" is "5", "Low" is "9" (which doesn't even exist in Nag). I do not know SyncMLs priority definition, so this could be a bug in Horde/Sync or Funambol. If this is a bug in Horde/Sync: Please fix. :-) If this is a bug in Funambol/Lightning: Please validate user input upon synchonization as these things tend to become overflows.