Team Calendars: Updates and Manual Changes

How the calendar list behaves on repeated migration runs and when users change it in SharePoint.

Synchronization is one-way

Changes flow from Confluence to SharePoint only. Nothing is written back to Confluence.

WikiTraccs recognizes its calendar lists by a marker in the list description (wt-calendar-id:...). Renaming the list is safe; WikiTraccs finds it again. Do not remove the marker from the list description, otherwise WikiTraccs creates a new list on the next run.
Events are matched by their source identifier. Changed source events update their list items, new source events are added.
Events that were deleted in Confluence are removed from the list. Only WikiTraccs-managed items are removed; see below.
When the source calendar has not changed since the last synchronization, WikiTraccs skips the list writes for that calendar.

Do not edit WikiTraccs-managed rows while further migration runs are planned. A managed row (it carries a source UID value) is overwritten with the source values on the next synchronization of a changed calendar. When the source calendar is unchanged, the synchronization skips writes, so manual edits are not repaired either. While migration runs are still happening, treat the generated lists as read-only mirrors. Once the migration is finished, the list is a normal SharePoint list and all rows can be edited freely.
Rows you add yourself are safe. Items without a source UID are never modified or deleted by WikiTraccs.

Cancelled events remain in the list as rows with status CANCELLED.
A calendar removed from Confluence is retained in SharePoint by default, including all its migrated events and its list. Removal of such lists can be enabled with the RemoveDeletedTeamCalendars feature flag in the configuration file.