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 344464 - Changing recurring appoint's calendar loses recurrance
Changing recurring appoint's calendar loses recurrance
Status: RESOLVED DUPLICATE of bug 329571
Product: evolution
Classification: Applications
Component: Calendar
2.6.x (obsolete)
Other All
: Normal minor
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-06-10 07:04 UTC by karlheg
Modified: 2006-06-10 13:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description karlheg 2006-06-10 07:04:34 UTC
Please describe the problem:
I made a class schedule appointment, but put it on the wrong calendar by mistake.  When I edited it and changed it from my "personal" calendar to the "class schedule" one, the "Save" button did not light up.  When I clicked the "close" button, I was prompted about whether to save the appointment, and I said "yes".  It then asked if I wanted that to apply to all or just this occurance.  I clicked "all", and then in the month view, I could see that there was only one instance of that class showing now, with the color changed to reflect that it is now in the correct calendar.  I editted the appointment again, and looked on the recurrence dialog, and found that it still had the recurrance attributes I had set earlier.  I unchecked and then rechecked the recurrance box, and after saving the appointment, it is displayed correctly.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 André Klapper 2006-06-10 13:41:08 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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