GitHub Copilot App の canvas で GitHub Issues のガントチャートを作ってみたBecause GitHub Projects lacks a full-featured Gantt chart view, this article…

GitHub Projects has become a popular way to plan work directly alongside code, yet it still lacks a full-featured Gantt chart view. A tutorial published on the Japanese developer platform Zenn addresses that gap by showing how to use the canvas feature in the GitHub Copilot App to generate a custom Gantt chart from GitHub Issues data. For teams that depend on timeline-based scheduling, which remains common in Japanese software development, the approach offers a way to produce a familiar deliverable without leaving the GitHub ecosystem.

GitHub Projects is a planning layer built on top of Issues and pull requests. It lets developers organize tasks into boards, tables, and roadmap-style views, attach custom fields such as status, priority, and iteration, and keep project tracking close to everyday development. The author of the tutorial highlights this consolidation as the main appeal, noting that being able to keep both routine development and project management on GitHub is something they value, and that they even use it for personal work task management.

The specific shortcoming the article targets is the absence of a true Gantt chart. GitHub Projects does provide a roadmap view that arranges items along a timeline, but the author describes it as only an approximation of what teams often want. Practical needs, such as exporting to Excel or supporting the detailed conventions of a particular workplace, are not covered. A Gantt chart, which plots tasks against a horizontal time axis to show start dates, durations, and overlaps, remains a standard artifact in many Japanese development settings, which makes the missing capability noticeable.

Instead of switching to a dedicated project management tool, the tutorial demonstrates bringing Issue data into the GitHub Copilot App and using canvas to build the chart. Canvas appears to function as an interactive workspace inside the Copilot App, where generated output can be viewed and refined directly rather than returned only as a chat reply. In this workflow, the assistant can take structured Issue information—titles, assignees, status, and any start and due dates recorded as fields—and render it into a chart that the user then adjusts through follow-up prompts.

This kind of workspace reflects a broader industry pattern. Comparable features have appeared elsewhere, such as ChatGPT's Canvas and Anthropic's Claude Artifacts, both of which give a persistent, editable surface alongside the conversation for code and documents. The common idea is to move beyond linear chat toward iterative creation, where a user can regenerate, tweak, and export a single artifact. Applying that model to GitHub data is a natural extension, because Issues already carry the structured metadata a scheduling chart requires.

A few prerequisites are worth noting for anyone attempting a similar setup. The quality of a generated Gantt chart dep