6.0.0-git
2019-08-24

[#8396] Send event change notifications to the organizer, if different
Summary Send event change notifications to the organizer, if different
Queue Kronolith
Queue Version Git master
Type Enhancement
State Assigned
Priority 1. Low
Owners mrubinsk (at) horde (dot) org
Requester marco.peterseil (at) openpartner (dot) at
Created 2009-07-02 (3705 days ago)
Due
Updated 2016-05-04 (1207 days ago)
Assigned 2015-12-23 (1340 days ago)
Resolved
Milestone 5
Patch No

History
2016-05-04 14:59:52 Michael Rubinsky Comment #6 Reply to this comment
Hi,
Event change notifications from an attendee to the organizer really
don't make any sense. What this ticket is really asking is true
support for COUNTER/DECLINECOUNTER and SEQUENCE numbers etc... Target
to get this into Horde 6/Kronolith 5.
When this version will be available? Is there any futurable date?
We don't have a specific date at this time.
2016-05-04 10:55:23 paco (dot) orozco (at) upcnet (dot) es Comment #5 Reply to this comment
Hi,
Event change notifications from an attendee to the organizer really 
don't make any sense. What this ticket is really asking is true 
support for COUNTER/DECLINECOUNTER and SEQUENCE numbers etc... 
Target to get this into Horde 6/Kronolith 5.
When this version will be available? Is there any futurable date?
2015-12-23 04:46:07 Michael Rubinsky Comment #4
Assigned to Michael Rubinsky
State ⇒ Assigned
Milestone ⇒ 5
Reply to this comment
This has been somewhat dealt with by the recent organizer support, 
though the only thing that triggers an update (really a REPLY) to be 
sent to the organizer currently is a change in attendance status for 
the attendee.

Event change notifications from an attendee to the organizer really 
don't make any sense. What this ticket is really asking is true 
support for COUNTER/DECLINECOUNTER and SEQUENCE numbers etc... Target 
to get this into Horde 6/Kronolith 5.
2009-07-11 02:58:48 Chuck Hagenbuch Summary ⇒ Send event change notifications to the organizer, if different
State ⇒ Accepted
Version ⇒ Git master
 
2009-07-10 06:10:43 marco (dot) peterseil (at) openpartner (dot) at Comment #3 Reply to this comment
Isn't user1 the organizer? Maybe the issue is that we don't send
notifications back to the organizer if an attendee moves the event?
yes exactly.
2009-07-10 00:40:20 Chuck Hagenbuch Comment #2
State ⇒ Feedback
Reply to this comment
Isn't user1 the organizer? Maybe the issue is that we don't send 
notifications back to the organizer if an attendee moves the event?
2009-07-02 11:32:16 marco (dot) peterseil (at) openpartner (dot) at Comment #1
Type ⇒ Enhancement
State ⇒ New
Priority ⇒ 1. Low
Summary ⇒ user who creates the appointment should be a default attendee
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
Reply to this comment
for example

User1 creates an appointment with User2 as attendee. User2 accepts. 
User2 changes the appointment time but User1 gets no notification 
'cause he isn't an attendee. There would be of course the possibility 
to manually insert User1 to the attendees though this isn't a very 
comfortable way to manage his calendar.



So I think every user who adds an attendee should also a attendee 
himself per default.

Saved Queries