Skip to content

Calendar Sync: Event Labeling and Organization Options #22

@krisrowe

Description

@krisrowe

Problem\nCurrently, synced calendar events are indistinguishable from native events on the target profile's primary calendar. This makes it difficult to manage or identify the source of synchronized data.\n\n### Proposed Options\n\n#### 1. Summary Prefixing (Labeling)\nPrepend the source profile name or a custom string to the event title during the import process.\n- Implementation: event['summary'] = f"[{source_profile}] {event['summary']}"\n- Pros: High visibility in all calendar views/apps; no extra calendar management.\n- Cons: Modifies the original title.\n\n#### 2. Dedicated Sync Calendar\nSync events to a separate calendar on the target profile instead of 'primary'.\n- Implementation: Provide tools to create a 'Synced Work' calendar and use its ID for the target.\n- Pros: Cleanest isolation; easy to toggle on/off in the UI; easy to bulk-delete.\n- Cons: Requires managing multiple calendars.\n\n#### 3. Event Coloration\nAssign a specific colorId to imported events.\n- Pros: Visual distinction without title changes.\n- Cons: Not all clients support colors well; may conflict with user's existing manual color coding.\n- Note: This can be used as a standalone option or in combination with prefixing/dedicated calendars (e.g., a specific prefix AND a specific color).\n\n### Analysis\nPrefixing is the most robust way to ensure visibility across all devices/apps. Dedicated calendars provide the best overall management experience. Event coloration adds a helpful secondary visual layer.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions