Closed
Bug 693039
Opened 13 years ago
Closed 13 years ago
Room booking
Categories
(Calendar :: Preferences, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: frsfrs, Unassigned)
Details
(Whiteboard: [support])
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Build ID: 20110928134238 Steps to reproduce: We are a group of people sharing a Sunbird calender for booking rooms. The calender is stored on a server and the people interact with it remotely on line. Every person has equal rights so that the rooms are usually assigned on a first-to-book-basis. Fairness in the group should normally avoid problems in overlaps. Actual results: Two persons of the group repeatedly deleted each other the bookings of a room causing clear booking problems. We realized that fairness is not enough and should be supported by a more strict/rigid software boundary. Expected results: The person attempting to cancel an event like the booking for a room should have been prohibited by the system. Each event (not each calender!!) should have a different degrees of ownership to allow only the original scheduler or the designated persons to cancel or to modify it. Preferably a log of the booking events of the single room could also be made available to track the successive booking operations on the room.
Comment 1•13 years ago
|
||
Sunbird is not actively developed anymore, you should switch to lightning... AFAIK the functions you want should be provided on the server side. You might look into calendar servers such as the apple calendarserver or davical. Disclaimer: I am not a developer of lightning, but just an active user.
Comment 2•13 years ago
|
||
Any kind of ACL functionality should not be part of the calendar client but the calendar server. -> INVALID?
Whiteboard: [support]
Comment 3•13 years ago
|
||
Yep, the ACL functionality is part of calendar server ! Closing the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•