Tickets :: [#8396] Send event change notifications to the organizer, if different

6.0.0-alpha10

5/14/25

Search Results: 252 of 573 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

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	07/02/2009 (5795 days ago)
Due
Updated	05/04/2016 (3297 days ago)
Assigned	12/23/2015 (3430 days ago)
Resolved
Milestone	5
Patch	No

05/04/2016 02:59:52 PM	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.

05/04/2016 10:55:23 AM	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?

12/23/2015 04:46:07 AM	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.

07/11/2009 02:58:48 AM	Chuck Hagenbuch	Summary ⇒ Send event change notifications to the organizer, if different Version ⇒ Git master State ⇒ Accepted

07/10/2009 06:10:43 AM	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.

07/10/2009 12:40:20 AM	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?

07/02/2009 11:32:16 AM	marco (dot) peterseil (at) openpartner (dot) at	Comment #1 Priority ⇒ 1. Low State ⇒ New Patch ⇒ No Milestone ⇒ Queue ⇒ Kronolith Summary ⇒ user who creates the appointment should be a default attendee Type ⇒ Enhancement	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.