Roadmap
Route: /analyst/roadmap
The Roadmap tracks connectors planned for development — which platforms the team intends to build, how important they are, how hard they'll be, and when work should ideally start. It's available to analysts and admins.
Layout
The page adapts to how many entries exist:
- Sparse (1–4 entries): the entry list and the timeline sit side by side, so the timeline fills the horizontal space.
- Dense (5+ entries): the full-width list stacks above the timeline.
At the top right, Add entry opens the entry form dialog.
Filters
Above the table:
- Search — matches against entry name, description, and reason.
- Priority dropdown — All / Low / Medium / High / Critical.
- Complexity dropdown — All / Low / Medium / High.
Entry table
| Column | Contents |
|---|---|
| Connector | Entry name, with a truncated description beneath |
| Priority | A badge: Low / Medium / High / Critical (see colours below) |
| Complexity | A badge: Low / Medium / High |
| Ideal start | The target start date |
| Docs | A "Docs" link opening the documentation URL in a new tab |
| Actions | A pencil (edit) and a trash (delete) icon |
Priority colours
| Priority | Colour |
|---|---|
| Low | grey |
| Medium | blue |
| High | orange |
| Critical | red |
Complexity colours
| Complexity | Colour |
|---|---|
| Low | green |
| Medium | yellow |
| High | orange |
Timeline
A visual timeline of all entries (ignores the table filters). Clicking an entry in the timeline scrolls the matching table row into view and briefly highlights it, so you can cross-reference the chronological view against the list.
Adding and editing entries
Add entry and the row pencil both open the same dialog. An entry captures its name, description, priority, complexity, ideal start date, documentation URL, and an optional reason. Saved entries are upserted into the list in place — no full reload.
Deleting entries
The trash icon opens a destructive confirmation dialog ("Remove {name} from the roadmap? This can't be undone.") with a spinner while deleting.
Roadmap changes are recorded in an audit log on the server side. The log isn't surfaced on this screen, but every add / edit / delete is captured for accountability.