Roadmap
Roadmap is currently in alpha. We'd love your feedback while we refine the experience and fill in the missing pieces.
Roadmap is Q's special page for curated product roadmaps. It gives you a public-facing view of what's planned, in progress, and shipped — connected to your actual dev missions and enriched with community input.
Use it when you want to:
- Communicate your product direction to users or stakeholders
- Collect feature requests and upvotes from the public
- Keep your roadmap in sync with real development progress
Core Concepts
Items
Each roadmap item represents a feature, improvement, or initiative. It has:
- A title and optional description
- A status: Planned, In Progress, Shipped, Requested, or Under Review
- An optional ETA (freeform text like "Q3 2026" or "July 2026")
- A category (e.g. Platform, Integrations, UX, Performance)
- Visibility: Public (shown on the public roadmap) or Internal (team-only)
- Source: Manual, Mission (linked from dev work), or Request (from the public form)
Categories
Default categories are provided (Platform, Integrations, UX, Performance) but you can customize them in the roadmap settings.
Statuses
| Status | Meaning |
|---|---|
| Planned | Committed to building, not yet started |
| In Progress | Actively being worked on |
| Shipped | Released and available |
| Requested | Submitted by a user via the public form |
| Under Review | Being evaluated by the team |
Mission Sync
Roadmap items can be linked to one or more dev missions from your mission boards. When a linked mission's status changes, the roadmap item status updates automatically:
| Mission Status | Roadmap Status |
|---|---|
| Backlog / Scoped | Planned |
| In Progress / Review | In Progress |
| Done | Shipped |
When multiple missions are linked, the roadmap item uses an aggregate status — it only becomes "Shipped" when all linked missions are done.
Linking missions
You can link missions when creating or editing a roadmap item. The item editor shows a searchable mission dropdown with missions from all your boards.
Unlinked Missions panel
Below the roadmap, an Unlinked Missions panel shows recent missions that aren't linked to any roadmap item yet. Click Add to Roadmap and Q's AI will create a user-facing roadmap item from the mission.
Changelog Links
Roadmap items can also be linked to changelog entries. This is useful when marking items as shipped — you can reference the changelog entry that announced the release.
AI Flow
Import from Missions
When starting a fresh roadmap, click Import from Missions in the toolbar. Q will scan all your mission boards and create roadmap items for scoped and in-progress work.
Suggest Items
Once you have items on the roadmap, the same button becomes Suggest Items. Q will review your missions and suggest user-facing work that would be valuable to add — excluding internal tasks like bug fixes and refactors.
Triage feature requests
When a user submits a feature request, the Request Inbox shows a Triage with AI button. Q will search your missions for related work, create a new mission if needed, and update the roadmap item accordingly.
Public Roadmap
Your roadmap can be shared publicly, independent of whether your project itself is public or private.
Making your roadmap public
- Open the Roadmap page in your project
- Click the Share button in the toolbar
- Toggle Public on
- Your roadmap URL uses the project's public slug (managed in Project Settings)
- Optionally add a Website URL and label for a "Visit website" link on the public page
What's visible
- Only items with public visibility are shown
- Internal items always stay private
- If "Show Requests" is enabled in settings, community-submitted requests are also shown
Public surfaces
- Standalone page at
/public/roadmap/[your-slug]— a full-page view with status columns, voting, and the feature request form - Embeddable via
<iframe>at/public/roadmap/[your-slug]/embed— a minimal-chrome version for embedding on your website - On heyQ itself at
/roadmap— heyQ's own product roadmap, powered by the same system
Embed code
The public settings dialog provides a ready-to-use <iframe> embed code snippet. Paste it into your website's HTML.
Voting
When voting is enabled (it is by default), visitors to your public roadmap can upvote items. Each visitor can vote once per item per 24 hours.
Vote counts are visible on the internal roadmap cards too, so you can see which features your users care about most.
Feature Requests
When feature requests are enabled, the public roadmap shows a Suggest a Feature form at the bottom. Submitted requests appear in the Request Inbox on the internal roadmap for you to triage.
Read counts
When a visitor clicks on a roadmap item to read its full description, a read is tracked. Read counts are visible on your internal roadmap cards alongside vote counts, giving you insight into which items attract the most attention.
Engagement Metrics
The internal roadmap cards show two engagement indicators:
- Upvotes (arrow icon) — how many public votes an item has received
- Reads (eye icon) — how many times visitors opened the item detail