circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

#538 Work-item sources: aggregate GitHub assignments, then Planner and kanban boards

–

  • github
  • github/openchronology/timeline-app
  • github/openchronology/timeline-app#538
  • issue
  • state:open
  • label:enhancement

Part of #533. OpenChronology as an **aggregator** of the events that work tools already create: GitHub issue and pull request assignments first, then Microsoft Planner and kanban boards. It mirrors them read-only; it is not a time tracker. Depends on ongoing durations (#537): an open work item is a duration that ends now. ## Model The same pattern as the [syslog receiver](docs/syslog.md), the [journald follower](docs/journald.md) and [`och-import-logs`](docs/log-import.md): an API key, routing rules to timelines, and a live path plus a backfill path. | Source event | On the timeline | | --- | --- | | Issue or PR opened | A duration from its creation, ongoing | | Closed or merged | The duration gets a fixed end | | Reopened | The end becomes ongoing again | | Assigned or unassigned | A moment, and an assignee tag on the duration | | Labels, milestone, repository | Tags | | Linked issues, "closes #n" | Relationships | Each work item keeps a stable ID derived from its source (`github:owner/repo#412`), so redelivered webhooks and re-runs of the backfill update rather than duplicate. ## GitHub, first - **Live:** a webhook receiver (`issues`, `pull_request` and `issue_comment` events if wanted), checking `X-Hub-Signature-256`, routing by repository. - **Backfill:** an importer that reads a repository's issues and PRs, and their timeline events, through the REST API with a token, with `--since` and `--dry-run` like `och-import-logs`. - **Gantt view:** check that separating by the assignee tag, plus relationships, gives a usable per-person chart before adding any new view. ## Later sources, same mapping - **Microsoft Planner:** tasks through Microsoft Graph (created, assigned, percent complete, completed), using change notifications for live updates. - **Kanban boards:** for example GitHub Projects, Trello or Jira. A card's time in each column becomes a duration, and a column move becomes a moment. ## Privacy Assignments name people, so this mirrors personal data from another service. The docs should say what is copied, and deleting or unassigning at the source should be reflected. https://github.com/circagraph/timeline-app/issues/538

Related

Open #538 Work-item sources: aggregate GitHub assignments, then Planner and kanban boards in the timeline

#538 Work-item sources: aggregate GitHub assignments, then…