View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0006036SOGoWeb Calendarpublic2024-09-11 15:142024-09-13 15:31
ReporterChristian Mack Assigned Tosebastien  
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionopen 
Product Version5.11.0 
Summary0006036: It is no longer possible to move a single instance of a series of repetitive Tasks into another calendar
Description

When using a repetitive Task, you can edit it with either "Edit This Occurence" or "Edit All Occurences".
But when you use "Edit This Occurence" and change the calendar to another one, all tasks of that series get moved to that calendar.

This caused some bewilderment and irritation here, as some later tasks where moved too and missed because of that.

Before it was possible to just move that one instance/occurence, and keep all other instances in the old calendar.
That is also what you expect when using "Edit This Occurence".

Steps To Reproduce

1) Go to calendar section "Tasks"
2) create a repeating task
3) edit one instance by choosing "Edit This Occurence"
4) change field "Calendar" to another calendar with write privilege
5) "Save" that change
=> the complete Task series gets moved to that calendar

Additional Information

I can reproduce that with nightlies on demo.sogo.nu

Hint:
For us it is not necessary to keep that moved single task instance as part of a task series.
It could be converted to a single task if that is easier to implement.

TagsNo tags attached.

Activities

sebastien

sebastien

2024-09-11 17:15

administrator   ~0017872

Hello Christian,

Do you know if this behavior has appeared in version 5.11 with fixed in ticket 0006031?

Sebastien
Christian Mack

Christian Mack

2024-09-12 12:41

developer   ~0017875

Hello Sebastien

This bug appeared in 5.11.0-Release.
I manually added the code change from 0006031 in our production system, in order to check again.
The fix for Bug 0006031 did not fix this problem.

Kind regards,
Christian
sebastien

sebastien

2024-09-12 16:43

administrator   ~0017876

Ok, thanks for reporting I will have a look on that next week

Sebastien
sebastien

sebastien

2024-09-13 11:23

administrator   ~0017878

FI this happens also on 5.10.0
sebastien

sebastien

2024-09-13 15:31

administrator   ~0017880

Dear Christian,

The behavior is the same for events.
Technically, the event (or task) is linked to a folder_id in the database. When one occurrence is modified, the iCalendar data is updated but still contains all occurrences.

BEGIN:VTODO
UID:840B-66E43180-3-34BF88C0
SUMMARY:Bar
CLASS:PUBLIC
RRULE:FREQ=DAILY;COUNT=10
DTSTART;TZID=Europe/Berlin:20240913T143000
DUE;TZID=Europe/Berlin:20240913T143000
CREATED:20240913T123604Z
DTSTAMP:20240913T123604Z
LAST-MODIFIED:20240913T123604Z
END:VTODO
BEGIN:VTODO
UID:840B-66E43180-3-34BF88C0
SUMMARY:Bar2
CLASS:PUBLIC
DTSTART;TZID=Europe/Berlin:20240914T143000
DUE;TZID=Europe/Berlin:20240914T143000
CREATED:20240913T123841Z
DTSTAMP:20240913T123841Z
LAST-MODIFIED:20240913T123841Z
RECURRENCE-ID:20240914T123000Z
END:VTODO

The iCalendar data is not split and remains associated with the same folder_id.

Previously, it was possible to move only one instance/occurrence while keeping all other instances in the original calendar.

I'm really surprised by this, given the product/code architecture. Do you remember which version of SOGo this was?

For us, it is not necessary to keep that moved single task instance as part of a task series.
It could be converted to a standalone task if that’s easier to implement.

I agree, but this needs significant changes.

Best,
Sebastien

Issue History

Date Modified Username Field Change
2024-09-11 15:14 Christian Mack New Issue
2024-09-11 17:08 sebastien Assigned To => sebastien
2024-09-11 17:08 sebastien Status new => assigned
2024-09-11 17:15 sebastien Note Added: 0017872
2024-09-12 12:41 Christian Mack Note Added: 0017875
2024-09-12 16:43 sebastien Note Added: 0017876
2024-09-13 11:23 sebastien Note Added: 0017878
2024-09-13 15:31 sebastien Note Added: 0017880