After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 769574 - setting dates in task list allows illegal DUE dates
setting dates in task list allows illegal DUE dates
Product: evolution
Classification: Applications
Component: Tasks
3.20.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Reported: 2016-08-06 10:08 UTC by Tim Ruffing
Modified: 2021-05-19 12:28 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Tim Ruffing 2016-08-06 10:08:50 UTC
Quoting about the DUE property for tasks:
For cases where this property is specified in a "VTODO" calendar component that also specifies a "DTSTART" property, the value type of this property MUST be the same as the "DTSTART" property, and the value of this property MUST be later in time than the value of the "DTSTART" property.

Using the context menu in the task list, it is possible to violate both of the requirements.

The first requirement (same value type/all-day) is related to bug 769573.

Regarding the second requirement, note that RFC 5545 even requires DUE > DTSTART as opposed to RFC 2445, which just requires DUE >= DTSTART.
In practice, requiring only >= seems to be okay, and it's not even clear if the change in the specification was intentional, see .

The bug is a problem for me, because my phone refuses to sync tasks violating the second requirement.
Comment 1 André Klapper 2016-08-07 12:12:57 UTC
Please provide Evolution version information by setting the "Version" field.
Comment 2 André Klapper 2021-05-19 12:28:47 UTC
GNOME is going to shut down in favor of 
As part of that, we are mass-closing older open tickets in (resources are unfortunately quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
and create a new bug report ticket at

Thank you for your understanding and your help.