Description metadata tag: open the board to any calendar client - #13
Merged
Conversation
Plan-IT stored work item and sprint metadata only in Google Calendar extendedProperties.private, which most calendar clients (including AI assistants restricted to basic Calendar APIs) cannot read or write. That made the board invisible to anything but this app. Events now also carry a machine-readable tag as the last line of the description, e.g. [planit kind=workitem; type=feature; status=active; priority=high] Readers prefer the tag and fall back to extendedProperties, so existing events keep working, and events created or updated by external clients (which can only edit descriptions) participate fully: classification in listProjectEvents also recognizes the tag. The tag is stripped from the user-visible description on read. This turns any calendar-capable client into a Plan-IT client.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Gardner-Programs
added a commit
that referenced
this pull request
Jun 26, 2026
…a-tag Description metadata tag: open the board to any calendar client
Gardner-Programs
added a commit
that referenced
this pull request
Jun 26, 2026
…a-tag Description metadata tag: open the board to any calendar client
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Item metadata lived only in Calendar
extendedProperties.private, which most calendar clients (including AI assistants limited to basic Calendar APIs) cannot read or write. The board was invisible to everything except this app.What changed
[planit kind=workitem; type=feature; status=active; priority=high; ...]extendedProperties(existing events keep working)Testing
tsc --noEmitclean. Verified end to end against live calendars via an external Calendar API client (read, status change, create).Merging auto-deploys via Vercel.