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 310844 - 'Copy to calendar' of recurring appointment doesnt work
'Copy to calendar' of recurring appointment doesnt work
Status: RESOLVED WONTFIX
Product: evolution-groupwise
Classification: Deprecated
Component: Groupwise Plugins/Features
unspecified
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
gnome[unmaintained]
: 352410 (view as bug list)
Depends on:
Blocks: 317266 327508 327510
 
 
Reported: 2005-07-19 07:44 UTC by Poornima
Modified: 2013-07-23 14:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30

Attachments
proposed evo patch (2.66 KB, patch)
2008-03-20 12:31 UTC, Milan Crha 		committed Details | Review

Description Poornima 2005-07-19 07:44:38 UTC 
Create a recurring appointment in GW calendar. Select it, right click and then
select 'Copy to Calendar'.
Result: Only one instance gets copied in different time slot
Comment 1 Poornima 2005-07-19 07:53:56 UTC 
Even 'Move to calendar' of recurring meeting & appointment doesnt work
Comment 2 Priit Laes (IRC: plaes) 2005-08-31 19:48:56 UTC 
Also happens on 2.2.3.

Copying an one-time appointment from local calendar to Exchange works, but when
the appointment is recurring it doesn't even copy one instance..
Comment 3 Matthew Barnes 2008-03-11 00:25:10 UTC 
Bumping version to a stable release.
Comment 4 Milan Crha 2008-03-20 12:26:43 UTC 
Move and Copy uses same code, the only difference is with delete or not delete at the end.
Comment 5 Milan Crha 2008-03-20 12:31:36 UTC 
Created attachment 107673 [details] [review]
proposed evo patch

for evolution;

Transfer master object instead of the instance for recurring events.
Comment 6 Chenthill P 2009-01-16 06:40:53 UTC 
Milan, there is one concern which I have with the patch. You remove the recurrence id if the master object is not obtained. IMHO you need to check whether its an exception (detached instance) by checking for the absence of rrule (e_cal_component_has_recurrences) to decide whether to remove the recurrence id or not. Please change that bit of the code and commit the patch.
Comment 7 Milan Crha 2009-01-16 11:23:54 UTC 
Slightly modified patch committed to trunk. Committed revision 37084.

As we discussed on IRC, do not remove RID for detached instances (those to whom _has_recurrences evaluates to false).

Anyway, this doesn't fix bug completely, as Chen suggested, we should ask, in case of detached instances, whether to move/copy all detached instances, or only those selected. Thus I'll keep bug opened.
Comment 8 Milan Crha 2010-05-26 20:20:55 UTC 
*** Bug 352410 has been marked as a duplicate of this bug. ***
Comment 9 André Klapper 2013-07-23 14:38:57 UTC 
evolution-groupwise provides connectivity to Novell Groupwise servers. The last stable release of evolution-groupwise was 3.4.2 which took place a year ago.

evolution-groupwise is not under active development anymore.

It is currently unlikely that there will be any further active development.

Closing this report as WONTFIX as part of Bugzilla Housekeeping.

Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again.