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 337406 - Make recurrent appointment moveable deletes entries.
Make recurrent appointment moveable deletes entries.
Status: RESOLVED DUPLICATE of bug 326964
Product: evolution
Classification: Applications
Component: Calendar
2.4.x (obsolete)
Other other
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks: 317266
 
 
Reported: 2006-04-05 16:53 UTC by Martin Klaffenboeck
Modified: 2006-04-05 20:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Martin Klaffenboeck 2006-04-05 16:53:30 UTC 
Distribution: Gentoo Base System version 1.6.14
Package: Evolution
Priority: Normal
Version: GNOME2.12.3 unspecified
Gnome-Distributor: Gentoo
Synopsis: Make recurrent appointment moveable deletes entries.
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: unspecified
Description:
Description of Problem:

When I make an recurrent apointment moveable, the original seems to get
lost somehow.

Steps to reproduce the problem:
1. Create an Appointment recurrent, from 8. March until 30. June, with
some exceptions, weekly, from 8:30 to 10:00
2. Make one of the appointmens moveable, because on the 5th of April it
goes from 8:30 to 11:00. 
3. Simply stretch the item with the mouse.

Actual Results:
You can see, that now the items befor this item are gone, afterwards
too.

Expected Results:
Only adding an exception to the original recurrent appointment, and add
a new appointment with the same data only on the date selected.

How often does this happen?
Not every time, I would suppose a 95% match of this problem while using
this way to get the new appointment.

Additional Information:
Evolution 2.4.2.1
evolution-data-server 1.4.2.1




------- Bug created by bug-buddy at 2006-04-05 16:53 -------
Comment 1 André Klapper 2006-04-05 20:28:55 UTC 
this is fixed in 2.6, i guess, at least i could reproduce this but have not seen it for a long time.

please reopen this bug if you can still see this in evo 2.6. thanks in advance.

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