GitHub Projects roadmap view: a complete setup

The roadmap is one of the three layouts a GitHub Projects view can use, next to table and board. It puts issues, pull requests and draft issues on a timeline using your project's date or iteration fields. This guide sets one up from an empty view, then covers what the roadmap can't do. It works without any other tool.

How do I turn a view into a roadmap?

Change the layout of a view from its View menu.

1. Open the project and create a view with + New view, or pick an existing view.
2. Click View next to the view's search bar.
3. Under "Layout", click Roadmap.

GitHub tries to use the date and iteration fields your project already has. Each view keeps its own layout, so a table called "Backlog" and a roadmap called "Quarter plan" can sit side by side over the same items.

Which date fields does the roadmap use?

Each bar runs from a start field to a target field, and you choose both.

1. In the top right of the roadmap, click Date fields.
2. Select a field for "Start date" and one for "Target date". Each can be a date field or an iteration field.
3. If the project has neither, click New field, type a name and click Save, then select it.

To add a date field outside the roadmap, click + in a table view's last field header, choose New field, select Date and save. Date fields have no default value, so items stay off the timeline until someone sets their dates.

Dragging a bar changes the item's fields: its start and target dates, or its iteration when the view uses an iteration field. A roadmap view is a scheduling tool as well as a picture.

How do I change the zoom?

Click the zoom control in the top right of the roadmap and choose Month, Quarter or Year. Month shows the most detail, and Year gives the widest overview.

What are markers, and how do I show milestones?

Markers are vertical lines on the timeline for key dates. Click Markers in the top right of the roadmap and choose which ones to show:

• Iterations from your iteration field.
• Milestones associated with the items in the project.
• Dates of the items in the project.

Milestone markers answer "which work lands before the release date?" at a glance. Combine them with a filter such as milestone:"QA release" to see only the work in one release. The filter syntax guide lists every qualifier a roadmap view accepts.

How do I group, slice and sort a roadmap?

Use the View menu, the same way as in a table.

• Group by splits the timeline into one group per value of a field, such as one per team or per milestone. You cannot group by title, labels, reviewers or linked pull requests.
• Slice by adds a side panel listing a field's values. Clicking a value narrows the roadmap to it, on top of the view's filter. You cannot slice by title, reviewers or linked pull requests.
• Sort orders items within each group, with an optional secondary sort.
• Field sum adds the total of a number field, such as an estimate, to each group's header once the view is grouped.

A useful quarter plan is a roadmap grouped by team, zoomed to Quarter, with milestone markers on and a field sum of your estimate field in each lane header.

What can't the GitHub roadmap do?

It covers one project, draws bars, and stops there. The limits worth knowing before you plan around it:

• One project at a time. A roadmap is a layout of one view in one project. Aggregating several projects into one organisation timeline is the most-upvoted ask in GitHub's community discussions (#157993) and has not shipped.
• No dependency lines. Sub-issues and blocked-by links live on the issues, but the roadmap draws neither. Gantt-style dependency views are a separate long-running request (#6803).
• Items without dates are invisible. There is no default date, so an unscheduled item has no bar until someone sets its fields.
• Some fields can't group or slice. Labels, reviewers and linked pull requests can't group a roadmap. Title, reviewers and linked pull requests can't slice it.

Dedicated planning tools do more here. Zenhub leads its marketing with real-time roadmaps alongside sprints, epics and release reports, priced at $8.33 to $12.50 per user per month (checked 2026-08-22). If your team needs dependency arrows or a roadmap across many projects, a tool like that fits better than GitHub's roadmap.

Does Gitsu have a roadmap view?

No. Gitsu has list and board views and no timeline, so a GitHub roadmap view does not open as a roadmap in Gitsu. Gitsu's own product research records this plainly: GitHub ships a roadmap layout and Gitsu does not, which makes the gap a step backwards for anyone who plans on github.com. The research recommends a modest single-project timeline over the iteration and milestone fields Gitsu already reads, without dependency arrows or cross-project views. Nothing from that recommendation has shipped, and there is no date for it.

For timeline planning, keep the roadmap on github.com. Gitsu does not change your project views, so the roadmap you set up there stays exactly as you left it.

What Gitsu does offer for dated work, per its code:

• Date filters. Date fields accept >, <, ranges and @today with an offset, so date:@today..@today+14d lists what is due in the next two weeks. Gitsu's offsets need a unit (d, w, m or y).
• Date and iteration sorting. Sorting by a date field orders items by date, and sorting by an iteration orders them by the iteration's start date.
• Boards by iteration or milestone. Choose Columns and pick an iteration or milestone field to get one lane per sprint or release. Iteration lanes run in start-date order and milestone lanes in title order. Lanes appear only for values that at least one card holds.
• A way back to GitHub. The project settings drawer has Open project settings on GitHub, and an item's detail view has Open on GitHub.

The iterations guide covers sprint planning in both tools, and the getting-started guide connects your first project to Gitsu.