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

#569 Plan work as a Gantt chart: forge due dates, roadmaps and Microsoft Project files

–

  • github
  • github/openchronology/timeline-app
  • github/openchronology/timeline-app#569
  • pull request
  • state:merged

Part of #538 and #533. **Builds on #568**: this branch contains #568's commit, so review the second commit (`Plan repositories' work as a Gantt chart`). The diff shrinks to it once #568 merges. ## Plans An item's or milestone's planned dates become a duration beside it, `Planned: #12 …`, tagged `planned`. Separating by `planned` sets the plan beside what happened: | Planned by | From | Until | | --- | --- | --- | | GitLab and Forgejo issues' due dates | creation | end of the due date | | Milestones' due dates (GitHub, GitLab, Forgejo) | GitLab's start date, else creation | due date | | GitHub Projects' roadmap fields | the start date field | the target / end / due date field, one plan per project | - **Importer:** reads GitHub Projects' dates through GraphQL, one request per 50 issues and per 50 pull requests. That needs a token that can read projects (`read:project`). Without one, the dates are left out with a warning. - **Receiver:** a `projects_v2_item` delivery whose **date** field changed rewrites the plan (or removes it when the target date is gone) and adds a `rescheduled` moment, such as `Target date set to 2026-11-12 in Roadmap`. ## Boards and dependencies - **GitLab issue boards:** a board's lists are labels. The importer reads the project's boards and turns list labels into `moved` moments and stays in each list. Labels changed together, as when an issue is dragged between lists, count as one move. - **Forgejo dependencies:** `add_dependency` and `remove_dependency` become `dependency added` and `dependency removed` moments, with a link. - **Forgejo project boards:** they stay out of reach. Forgejo's API has no project endpoints, and its timeline only says an issue joined a project, never which column. The docs say so. ## Microsoft Project files `och-import-github --plan ` reads Microsoft Project XML (MSPDI), which Microsoft Project, ProjectLibre and GanttProject all save: - **Plan:** each task's start and finish become its planned duration. Milestones are moments. - **What happened:** its actual start and finish become a duration of its own. A task not begun has only its plan. - **People and phases:** resources are its people, and its summary tasks are its labels (phases). - **Links:** its predecessors and its summary task. - **Time zone:** the files' times have no zone, so `--time-zone` says which zone they are in (UTC by default). Checked on MPXJ's real sample files (`mspdirelations.xml`, `mspdinulltasks.xml`, `baselines.xml`, `mspdiassignmentfields.xml`): tasks, null tasks, predecessors, resources and baselines come through. ## Tests - **New:** `test/forge-plans.test.mjs` covers the plans, roadmap reading with paging, the receiver rewriting a plan, board moves and dependency links. - **Updated:** existing expectations, for milestone plans. - **Real GitHub:** the GraphQL roadmap query ran against this repository through `gh`. GitHub checked its fields and refused it only for the missing `read:project` scope. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/circagraph/timeline-app/pull/569

Related

Open #569 Plan work as a Gantt chart: forge due dates, roadmaps and Microsoft Project files in the timeline

#569 Plan work as a Gantt chart: forge due dates, roadmaps…