Skip to content

The roadmap

Hussein Jarrar edited this page Sep 12, 2026 · 2 revisions

The roadmap is a timeline of scheduled work: a bar per item, grouped under its epic. Like every other view, it is a saved query with a display.

A roadmap is a view

A roadmap is a saved view whose type is Roadmap — the same kind of object as a Board or a List. It has its own query, sharing and ownership. The old /p/<project key>/roadmap link still works. It redirects to the project's first roadmap-type view, or to the project's home page if the project has none.

Because a roadmap is a view, it inherits everything covered in Views: an editable SLQ query, quick-filter chips, and sharing.

The timeline

The Roadmap view for the RADD project: an empty timeline with the message "No scheduled items yet — set a start and target date on an item, or drop one here from the Unscheduled tray," a toolbar with zoom, Today, Dependencies, Epics only and Show closed controls, and an Unscheduled tray on the right listing 42 items

The roadmap toolbar and the Unscheduled tray. This project's roadmap is empty because none of its items carry both a start and a target date yet — the empty-state message names the fix.

Each bar on the timeline is one item. A bar needs both a start date and a target date. An item with only one, or with neither, has no bar — it stays in the Unscheduled tray on the right instead.

An epic with its own start and target date draws a normal bar. An epic with no dates of its own, but with scheduled children, draws a dashed bar instead. That dashed bar spans its earliest child's start to its latest child's target. It tracks the children automatically, and you cannot drag it directly.

Start and target dates

A bar's position comes from the item's start_date and target_date fields — the same fields you can set on the item page. Nothing on the roadmap computes a schedule on its own. The two exceptions are a derived epic bar's span (above), and the Auto-schedule children action on an epic's right-click menu.

The category bars

A bar's fill color is the item's workflow state category. Radd uses the same six categories everywhere: triage, backlog, todo, in progress, done, and canceled.

A leaf item's bar is a solid fill. An epic's bar is a lighter, translucent shade of the same color, with a border. The lighter fill and border make an epic read as a container, not a single piece of work. Done and canceled items share one dark slate color, by design — both are out of play.

The resizable gutter

The row-label column on the left is a gutter, not a fixed sidebar. Drag the divider between the labels and the timeline to resize it. A bar with no visible label is an anonymous rectangle, so widening the gutter trades timeline width for readable names. Radd saves the width per view.

Dependencies shown on the timeline

Click Dependencies to turn connector lines on and off between bars linked by a Blocks relationship. Click a connector to retype or remove the link.

Drag from the small circle at a bar's edge onto another bar to create a link. A popover lets you select its type at the drop point. A bar drag carries its dependents along the timeline. Hold Alt while dragging to move only that one bar, with no cascade.

A red Depends on chip appears past a bar's end whenever its blocker is not visible. That happens when the blocker scrolls out of view, a filter hides it, or Dependencies is turned off.

Changing a date from the roadmap

With edit access to the view — the same item.update permission atom other views use for dragging — you can reschedule an item from the timeline itself.

  • Drag the middle of a bar to move it. Both dates shift by the same number of days.
  • Drag either edge of a bar to resize it. Only that one date changes.
  • Drag an item from the Unscheduled tray onto the timeline to give it a start and target date.

Nothing you drag saves right away. Every gesture edits a local draft first, with undo and redo. Click Save in the toolbar to write your changes, or Discard to throw them away.


Mirrored from project.radd-hq.com on 2026-09-12. Documentation is written there; this copy is regenerated by scripts/publish_wiki.py and hand edits do not survive it.

Clone this wiki locally