Limiting notifications to origin calendar when using propagation workflows
under review
J
Jonathan Piper
When using calendar propagation, multiple calendars end up creating notifications. I am propagating between several calendars (i.e. Personal, Family, Work) so don't have one single source of truth and would prefer to not create an entirely new calendar for notifications. It would be ideal if Morgen could prevent notifications on the duplicated event.
J
Justin Bird
+1 from me, I have one workflow that I send entries from my personal calendar to my work calendar to block out the time, I'm trying to depersonalise it using nerd mode. Here's my mapEvent:
workflow.mapEvent = (originalEvent, mirrorEvent) => {
// Change title
mirrorEvent.title = "Personal Commitment";
// Remove alerts
mirrorEvent.alerts = {};
// Remove location
mirrorEvent.locations = {};
return mirrorEvent;
}
Which works for title and location but not notifications. If I look at the item in calendar it doesn't have an alert on it, but it still notifies anyway. Presumably overridden by "reminders for timed events". So some sort of "remind about propagated events" tickbox at calendar level would be cool.
Danny Hatcher
under review