You can use a roadmap on its own, or connect it to customer feedback and release announcements. Start by creating a roadmap, then choose how your team and customers will use it.
| Your goal | View or guide |
|---|---|
| Show what is now, next and later | Status columns |
| Plan dates, milestones and ongoing work | Gantt timeline |
| Plan internally by date but show customers simple columns | Separate internal and customer views |
| Compare work in a table | Open the roadmap table and save column views |
Assign a team and people, add an estimated delivery date and use custom fields for details your process needs.
Link related or dependent work. The link records the relationship; it does not calculate delivery dates for you. Keep team discussion in internal comments, and use formatted text and attachments to explain the work.
Use board access settings for public, signed-in, admin-only or selected-group access. Hiding navigation alone does not make a board private.
In Board settings → Voting & comments, choose whether to allow votes and comments. Use Customer posting to control new submissions. Turn these off when the roadmap is only for sharing plans. Check the public layout and filters in Preview as customer.
Share the board link, connect a custom domain, or embed a roadmap widget.
When you use feedback too, link requests to roadmap work. Use prioritization to compare ideas before you add them to the plan.
Connect Jira or Azure DevOps to link work and map statuses. For a custom connection, use the API, webhooks or MCP.
When work ships, publish a changelog update and choose which followers and subscribers to notify.