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 266629 - New meeting default start time should not be in past
New meeting default start time should not be in past
Status: RESOLVED DUPLICATE of bug 231166
Product: evolution
Classification: Applications
Component: Calendar
2.0.x (obsolete)
Other All
: Normal trivial
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-09-22 19:26 UTC by Raul Acevedo
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Raul Acevedo 2004-09-22 19:26:31 UTC 
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
New meeting requests always default to 9am.  Even if it's noon.  :)

Steps to reproduce the problem:
1. Click on New -> Meeting -> Scheduling.

Actual Results:
Start time defaults to 9am, even if it's past 9am.

Expected Results:
Should default to the next 30 minute slot.  I.e. if it's 1pm or 1:15pm, use
1:30pm.

How often does this happen? 
Every time.

Additional Information:
Comment 1 André Klapper 2004-12-27 18:35:15 UTC 
closing as discussed with gerardo on irc.

*** This bug has been marked as a duplicate of 231166 ***