updated the commets, will update the patch if we are clear with the way to go.

I didn't test every recurrence type (daily, weekly, monthly, yearly) from the iterface. Because I relay on the test case from kcalcore.

D11 & D12 are for T354

D11

i would fix kcalcore to not add these fileds to dirty, if they were not changed.

we have detection, when to reset partstatus in akonadi/calendar/incidencechange.cpp (line 1059ff) only if:

what is not working here?

we have written code for the collenview , that actually creates person nodes for collections.
If we would use this logic, to know to whom is the owner of a calendar -> we can change their status.
Email&real name can be requested via LDAP.

still can't test this, cause resource accept policy is auto accept.

jane.doe:

• creates new task folder
• adds permisson to write for john.doe
• creates a task

no need to do this with kontact

• create an event with "confidential"
• other user can't see the event
• the busy information is updated

I can do that for my kolabsys account with my lokal kontact (4.13.0.1)

can do that for my kolabsys account with my lokal kontact (4.13.0.1)

can do that for my kolabsys account with my lokal kontact (4.13.0.1)

can do that for my kolabsys account with my lokal kontact (4.13.0.1)

• accept/decliend buttons are visiable for invitation

• accept/decliend buttons are visiable for invitation

• creates event with many attachments and an attendee
• attendee see the attachment and can view them
• no special about different file formats

• create event with
• attachments

*see mail sent

• make sure that the attachments are viewavle for attendees

same as T296

• open calendar
• change the status of an event
• see mail sent and the chagnes status

• change inviation handling to "ask for ech attendee"
• create event with attendees
• unselect attendees when the dialog pops up

• no special thing visiable ( another test series)

• no special thing visiable ( another test series)

• no special thing visiable ( another test series)

T326

The problem is that korganizer has no understanding of "delegated calendar", it mostly do the right, because organizator/attendee is unique. But this approch will fail if there are events with both (delegator and delegated person) are in.

T326

• this is only if freebusy data is avaialble

• awnser with tentative at an invitation

• accept a invitation

• decline a event

• cancel event with datetime
• sent mail

• create evnet
• look if event is visiable in calendar
• and in "open calendar" for attendees

• create event series
• change one date&time
• reset the status for this exception

• only for thisandfuture

• create event series
• change with thisandfuture the date&time
• reset status for these exceptions

• create event series
• delete one occurence

• events series with date time instead of date only and with attendees

T354

problem T353

problem T354

T354

• create event series
• change date & time
• reset the status of all attendees