New Member
I tried looking to find a solution to a problem that I see. Sorry if it is a duplicate.
I have an event that goes from 6p-7p. I have another event that goes from 7p-8:30p. I have a 3rd event that goes from 8:30p-9:30p. Each have a different room scheduled in the same building.
If I add a cleanup time of 30 min to the 7p event, on the calendar the 8:30p even look like it starts at 9p. The more time I add, the later the 8:30p event appears in the calendar. It still says 8:30p, but in the week view it looks later than scheduled.
For the pictures, I removed the cleanup time.
If I add a setup time of 30 min to the 7p event, on the calendar the 6p event starts looking like it does not go as long. If I set the time for 1 hour setup time, the 6p event no longer appears on the calendar, but does look like it is merged with the 7p event.
I would think the setup and cleanup times would be with the event and the events should appear skinny, showing the overlap with the setup/cleanup times.
I have tried Firefox and Chrome: both give the same result.
Any suggestions for a fix or is this a bug?
I have an event that goes from 6p-7p. I have another event that goes from 7p-8:30p. I have a 3rd event that goes from 8:30p-9:30p. Each have a different room scheduled in the same building.
If I add a cleanup time of 30 min to the 7p event, on the calendar the 8:30p even look like it starts at 9p. The more time I add, the later the 8:30p event appears in the calendar. It still says 8:30p, but in the week view it looks later than scheduled.
For the pictures, I removed the cleanup time.
If I add a setup time of 30 min to the 7p event, on the calendar the 6p event starts looking like it does not go as long. If I set the time for 1 hour setup time, the 6p event no longer appears on the calendar, but does look like it is merged with the 7p event.
I would think the setup and cleanup times would be with the event and the events should appear skinny, showing the overlap with the setup/cleanup times.
I have tried Firefox and Chrome: both give the same result.
Any suggestions for a fix or is this a bug?

