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 271763 - New appointment dialog doesn't show Scheduling tab
New appointment dialog doesn't show Scheduling tab
Status: RESOLVED DUPLICATE of bug 263581
Product: evolution
Classification: Applications
Component: Calendar
2.4.x (obsolete)
Other All
: Normal normal
: Future
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-01-26 02:20 UTC by Raul Acevedo
Modified: 2012-04-03 09:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Raul Acevedo 2005-01-26 02:20:04 UTC 
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:
If I schedule a new appointment, I have no way of knowing where to fit it
in my schedule because there is no Scheduling tab.  Only the meeting
request dialog has a scheduling tab so I can see if there's a conflict.
Comment 1 Raul Acevedo 2005-04-28 23:20:18 UTC 
This is still an issue in 2.3.1.  Is this a deliberate UI decision?
Comment 2 JP Rosevear 2005-05-04 13:46:00 UTC 
Correct, it is deliberate to distinguish between a meeting and an appointment
(no attendees).
Comment 3 Raul Acevedo 2005-05-04 15:30:56 UTC 
How can I look at my schedule so my appointment doesn't conflict?

I would think you would still need the scheduling tab, just without the ability
to add other attendees... otherwise how can I tell if the appointment conflicts
with something else on my schedule?
Comment 4 Chenthill P 2005-08-04 18:28:40 UTC 
This can prolly be taken up for 2.6.
Comment 5 Matthew Barnes 2008-03-11 00:25:04 UTC 
Bumping version to a stable release.
Comment 6 André Klapper 2012-04-03 09:23:04 UTC 
Same as bug 263581 (this is just one way to solve it)

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