[BUG] Busy wildcard not functional

[kalani-gordon]

When "Busy" or "busy" is listed in Wildcard with the extension enabled, Cal Merge does not register the events to be merge-worthy when event is listed on multiple calendars

[HCAWN]

Hi Kalani,

I think I can see the issue, you have an "uncommon" configuration where a busy event is to the left of a titled event and so a match doesn't take place. I'll have a look at the matching alg and see what I can do. Out of curosity, how are you viewing other cals for the order of events to be like this? I presume both of these events are not from your calendar, the "first" Busy event is another persons calendar who has the event as private, and the "second" event with the title is yet another persons cal who doesn't have their event as private?

H

[kalani-gordon]

H — Correct to the uncommon configuration.

In this scenario, I'm using Notion Calendar to "block" events from Calendar A by default as busy onto Calendar B. Applicable to both calendars shared to me (across domains), as well as calendars I own.

As a user, I want to be able to add an event to a personal calendar, and block off on my primary work calendar with privacy with limited additional user interaction/duplication.

That said, it works in some scenarios, but not all. Only thing I can delineate is permissions levels.

[paul-job]

I have the same issue and use the same configuration. instead of using notion to create "blocks" in my professional calendar, I created an app script to do that, so the event with "busy" is on the left but being created by the user owning the calendar itself, instead of being sync-ed from an external source.

this becomes