Accept tasks with DUE=DTSTART
Closed this issue · 3 comments
See bitfireAT/davx5-ose#243. Proposed solution:
As the DUE>DTSTART constraint is enforced by OpenTasks (which is not recommended anymore), we could drop DTSTARTs that are >= DUE only when OpenTasks is the tasks backend. So if jtx Board and tasks.org accept tasks with DTSTART=DUE, we could sync such tasks to those backends as they are. Then everything including the alarms should be retained. For OpenTasks, we keep everything as it is because it's legacy code and will be removed sooner or later anyway.
Also relevant for @TechbeeAT @patrickunterwegs (jtx Board UI changes for DTSTART=DUE as discussed in chat).
@rfc2822 , would you drop the whole constraint and allow also DUE > DTSTART or just open up the possibility for DUE=DTSTART?
I'd like to technically accept as much as possible (also DTSTART>DUE) but I think the user should not be allowed to enter such invalid values in the UI.
Tasks.org uses a fork of ical4android that allows start=due (but not start>due). I'm not aware of it causing any issues