![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
How to make your administrative assistant cry: first, schedule a meeting with a complicated repeat schedule.
Then, have the calendar software entirely unable to handle the repeat in one meeting.
Make sure the meeting involves no fewer than 30 people.
After that, wait a month and make sure the repeat schedule of the second meeting is fucked up.
When the admin apologetically changes the meeting, don't actually fix it.
Don't fix it the second time either.
By this time, your admin should be leaking tears of frustration and trying to decide between the rum in her own desk drawer, raiding the gin in her one friend's desk, or the vodka in her other friend's desk. Or maybe crawling under her desk and not coming out for an hour.
Make sure your admin posts about the woes to the tech support forum before calling the helpdesk to yell a bit.
Why, yes, deleting the whole series and creating it again is one way to do it, but that lacks both elegance and the spirit of troubleshooting. Which is a great topic for a passive-aggressive follow-up comment in the forums.
Oooh, the engineer in the forums agrees with me.
At this point it helps if your admin is stubborn and also remembers that the creation was a little weird.
Your admin should remember to keep the "MOTHERFUCKER" out of the "I DUPLICATED THE MOTHERFUCKER" when posting to the forums in triumph.
When the engineer duplicates it too and files a ticket, have someone around for your admin to recount the tale to.
For the record? Until this is fixed, duplicating repeating calendar events is unwise when using the little platform that sometimes could, unless it is okay if the repeat cannot be changed.
Then, have the calendar software entirely unable to handle the repeat in one meeting.
Make sure the meeting involves no fewer than 30 people.
After that, wait a month and make sure the repeat schedule of the second meeting is fucked up.
When the admin apologetically changes the meeting, don't actually fix it.
Don't fix it the second time either.
By this time, your admin should be leaking tears of frustration and trying to decide between the rum in her own desk drawer, raiding the gin in her one friend's desk, or the vodka in her other friend's desk. Or maybe crawling under her desk and not coming out for an hour.
Make sure your admin posts about the woes to the tech support forum before calling the helpdesk to yell a bit.
Why, yes, deleting the whole series and creating it again is one way to do it, but that lacks both elegance and the spirit of troubleshooting. Which is a great topic for a passive-aggressive follow-up comment in the forums.
Oooh, the engineer in the forums agrees with me.
At this point it helps if your admin is stubborn and also remembers that the creation was a little weird.
Your admin should remember to keep the "MOTHERFUCKER" out of the "I DUPLICATED THE MOTHERFUCKER" when posting to the forums in triumph.
When the engineer duplicates it too and files a ticket, have someone around for your admin to recount the tale to.
For the record? Until this is fixed, duplicating repeating calendar events is unwise when using the little platform that sometimes could, unless it is okay if the repeat cannot be changed.
