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 300216 - broken date validation in evolution task lists
broken date validation in evolution task lists
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Tasks
2.2.x (obsolete)
Other other
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-04-11 16:44 UTC by nathanh
Modified: 2005-08-11 22:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description nathanh 2005-04-11 16:44:06 UTC
Distribution: Debian 3.1
Package: Evolution
Severity: normal
Version: GNOME2.10.0 2.2.1
Gnome-Distributor: Ubuntu
Synopsis: broken date validation in evolution task lists
Bugzilla-Product: Evolution
Bugzilla-Component: Tasks
Bugzilla-Version: 2.2.1
Description:
Description of Problem:
Creating or modifying a task but leaving the "Date completed" field with
the default of None results in a Validation Error after clicking OK.

Steps to reproduce the problem:
1. Click New Task
2. Enter anything for the Summary
3. Click OK

Actual Results:
Error Dialog appears containing the string "Validation error: Completed
date is wrong".

Expected Results:
Task should be created with the Date Completed as the default of None.

How often does this happen?
Reproducable every time.

Additional Information:
Changing the Date Completed field to the current date (by clicking the
dropdown and clicking Today) also produces the validation error dialog.
However changing the Date Completed field to yesterday's date, then
changing the date back to None, then clicking OK, allows the task to be
created correctly.




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-11 12:44 -------


Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "Evolution".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 André Klapper 2005-04-12 18:31:00 UTC
i have also seen this in snapshots about ten days ago, but now this bug seems to 
have gone... could you please test this again if this will be fixed in 2.2.2 
(should be out pretty soon)? thanks in advance.
Comment 2 nathanh 2005-04-16 11:40:54 UTC
I've just installed 2.2.2 and I can no longer reproduce the bug. Looks like it
has been fixed.
Comment 3 Aginesh Srinivasan 2005-05-24 11:37:27 UTC
i could not reproduce this bug in 2.2.2. I think the status of this bug could be
changed
Comment 4 Khasim Shaheed 2005-05-24 11:47:33 UTC
Are you still facing this issue?
Comment 5 nathanh 2005-05-24 11:59:11 UTC
See the comment I added April 16...

  --- Additional Comment #2 From nathanh@manu.com.au  2005-04-16 11:40 UTC -----

   I've just installed 2.2.2 and I can no longer reproduce the bug. Looks
   like it has been fixed.

I cannot reproduce in 2.2.2 either. The bug is fixed.
Comment 6 Chenthill P 2005-08-11 22:07:29 UTC
closing this bug as the reporter doesn't face the issue with upgraded version.