GitHub milestones as groups
Each milestone becomes a group with a diamond on its due date, with its issues beneath it and sub-issues nested under their parent. Drag the diamond and the milestone's due date moves in GitHub.
See your issues and milestones on a Gantt chart, across repositories. Set blocked-by dependencies and drag issues to new dates, and GitHub gets both.
No spam. The GitHub integration is in invite-only beta, and we'll email you when your invite is ready.
The question people search
Not really. GitHub Projects has a roadmap layout that places a project's issues on a timeline by their date fields.
Ganttify works with GitHub in two ways. Chart your repositories, with each milestone as a group and every issue and sub-issue as its own row, or chart a GitHub project, with its items grouped by status and their date or iteration fields as time blocks. In both, GitHub's blocked-by relationships show as dependencies, and a dependency you set on the chart becomes blocked-by in GitHub.
Everything you need
See which issues belong to each release and which ones hold it up.
Each milestone becomes a group with a diamond on its due date, with its issues beneath it and sub-issues nested under their parent. Drag the diamond and the milestone's due date moves in GitHub.
Drag an issue and Ganttify writes its start and target dates to the Start date and Target date issue fields, or to your project's date fields if you prefer.
Blocked-by relationships show as dependencies on the chart, and a dependency you set on the chart becomes blocked-by in GitHub. When one issue slips, the ones after it move along.
Chart a project as it is: items grouped by status, their date or iteration fields as time blocks, and dependencies between items.
Pick repositories from any organization and put them on one chart, each as its own group, with dependencies from an issue in one to an issue in another.
Share a read-only link with clients and leadership. They follow release dates and progress without a GitHub seat or a Ganttify account, and the chart updates as your issues move.
Plan your releases on a GitHub Gantt chart
How it works
The integration is in invite-only beta, so it starts with the waiting list.
Leave your email and you're on the list for the beta.
We email you as soon as your invite is ready.
Connect your GitHub account and pick the repositories or the project to put on your timeline.
How would you use a Gantt chart with GitHub? Your answer shapes what we build next during the beta. Mapping a launch across five repositories, or running everything off milestones?
Share how you'd use itQuestions
The short answers. For everything else, the help center has the long ones.
The roadmap layout places a project's items on a timeline by their date fields. Ganttify charts your repositories or a project with milestones as groups, sub-issues under their parent and blocked-by dependencies you can set on the chart, across repositories too.
GitHub lets you mark an issue as blocked by another. Ganttify shows those relationships as dependencies on the chart, and a dependency you set on the chart becomes blocked-by in GitHub; remove it and it goes. This works across repositories on one chart. A dependency that touches a milestone or a draft stays in Ganttify.
Each milestone becomes a group on the chart with a diamond on its due date. Its issues sit beneath it as time blocks and sub-issues nest under their parent, so you see how far each release has come. Drag the diamond and the due date moves in GitHub.
Yes. Select repositories from any organization and they land on one Gantt chart, one group per repository, so a release that spans your frontend and your API reads as one plan.
No. Ganttify works directly with issues and milestones. In an organization, issue dates go to GitHub's own Start date and Target date issue fields by default; for a personal repository, or an organization without those fields, Ganttify keeps the dates itself. If you do use Projects, you can chart a project directly or keep issue dates in its date fields.
Yes. Drag an issue to a new date and its Start date and Target date fields update in GitHub, or the date fields of the project you chose. Set a dependency and the blocked-by relationship appears in GitHub, and an issue you mark complete on the chart closes in GitHub. Changes made in GitHub show on the chart the next time it loads.
Yes. Share a read-only link to your Gantt chart. Clients and stakeholders see the roadmap without a GitHub or Ganttify account, and it updates as your issues change in GitHub. To plan releases together, share the chart with your team and decide who can view it and who can edit it.
Your issues, milestones and projects stay in GitHub, and the dates and dependencies you change on the chart are saved there too. Ganttify adds a planning layer on top for the rest: your chart settings, hidden rows and the colors of your time blocks, dependencies that touch a milestone or a draft, and issue dates when you choose to keep those in Ganttify.
It's an invite-only beta. Join the waiting list and we'll send you an invite as we widen access. To tell us how you'd use it, email [email protected].
Every integration
Dependencies, sharing and export work the same way for every integration. Connect yours, pick a project and your first chart is there.
Join the waiting list and we'll email you when your invite is ready.
Also available for Trello, Basecamp, Todoist and Google Calendar.