Community Administrator
With v2, it appears that building schedulers have completely lost the ability to override reservations. When a building scheduler tries to create an event (or modify an existing event) that uses a resource on a date/time that has already been reserved by a Reservation (not by an event), he or she cannot create that event. Instead, a message appears saying that they should contact the building scheduler (themselves!).
This limitation occurs for Blocked reservations as well as for reservations for a particular unit.
On v1, building schedulers could always schedule events on top of reservations (called "assignments" on v1) for their assigned building. This is an important capability for building schedulers to have. Without it, Blocked reservations are far too powerful, since they completely stop the resource from being scheduled by anyone. And it makes it so that the building scheduler cannot work out exceptions to repeating reservations, except by going back to the reservation and making an exception there, which is tedious and may create a bigger exception than was intended for a single event.
I have to think this is a bug -- I can't imagine that this capability was removed intentionally. Or am I missing something in how it works on v2?
There have been a couple of posts that hinted at this problem here and here, but I thought it was important enough to get a clear statement of the problem in a thread of its own.
This limitation occurs for Blocked reservations as well as for reservations for a particular unit.
On v1, building schedulers could always schedule events on top of reservations (called "assignments" on v1) for their assigned building. This is an important capability for building schedulers to have. Without it, Blocked reservations are far too powerful, since they completely stop the resource from being scheduled by anyone. And it makes it so that the building scheduler cannot work out exceptions to repeating reservations, except by going back to the reservation and making an exception there, which is tedious and may create a bigger exception than was intended for a single event.
I have to think this is a bug -- I can't imagine that this capability was removed intentionally. Or am I missing something in how it works on v2?
There have been a couple of posts that hinted at this problem here and here, but I thought it was important enough to get a clear statement of the problem in a thread of its own.
Questions that can benefit the larger community should be asked in a public forum, not a private message.