By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 254 - Assign appointment to wrong calendar
Summary: Assign appointment to wrong calendar
Status: RESOLVED WORKSFORME
Alias: None
Product: TDE
Classification: Unclassified
Component: tdepim (show other bugs)
Version: 3.5.13.x [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2010-09-03 13:54 CDT by John A. Sullivan III
Modified: 2018-07-27 04:27 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String: 3.5.11 (Trinity)
Application Version: 3.5.12-0debian6+r1170472
Application Name: KOrganizer

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John A. Sullivan III 2010-09-03 13:54:46 CDT 
I am using several calendars.  Normally, when I create a new appointment, I am presented with a list of calendars to which I can add the appointment. At least four times now (the first time I thought it was some stray mouse click), Korganizer has automatically added the appointment without asking (and to the wrong calendar which is how I noticed).  Moreover, there is no way to change the calendar to which the appointment belongs after it has been created (I'll open as a separate request for enhancement).  Thanks - John
Comment 1 Timothy Pearson 2010-09-03 13:57:31 CDT 
That's strange.  How are you creating the new appointment?

When I created an appointment by double-clicking the agenda view, after I clicked OK on the new event dialog another dialog popped up asking which resource the new event should be saved to.
Comment 2 John A. Sullivan III 2010-09-03 15:59:11 CDT 
It's very random and rare. That's why I initially dismissed it but it happened several times today.  Usually, I drag the length of the appointment and just start typing.  As strange as it sounds, it seems most of the problems today were when the first character typed was a "d" or "D".  I'd imagine that's entirely coincidental.  Since it is difficult to reproduce, it is difficult to get sufficient data to troubleshoot.
Comment 3 Timothy Pearson 2010-09-03 16:17:57 CDT 
By any chance do you start typing before the new event dialog comes up all the way?  It is possible a keystroke or two is being cached...

This would all be resolved if the resource list was integrated into the event editor a you suggested.  I don't have the time to do that level of modification for free at this point, but maybe sometime in the future. ;-)
Comment 4 John A. Sullivan III 2010-09-03 16:34:32 CDT 
I almost always do.  The typing in the selected appointment space initiates the dialog box.

I certainly appreciate the financial constraints.  That's why I opened the corresponding RFE as it is not a high priority for us and thought we just toss into the idea queue.  Thanks - John
Comment 5 Darrell 2013-05-22 19:46:22 CDT 
Is this report still valid?
Comment 6 Michele Calgaro 2018-07-27 04:27:52 CDT 
Can't reproduce and too long inactivity.
Closing as won't fix. Feel free to reopen the bug if you can reproduce this systematically, and please provide detailed instructions for that.