Confluence Roadmap: How to Build One Your Team Keeps Up to Date
8 min read ยท 2026-10-25
You can build a Confluence roadmap in two main ways: draw it with the Roadmap planner macro (lanes, bars and markers on a timeline) or embed a timeline that already lives in Jira with the Jira timeline macro. The Roadmap planner suits high-level plans you edit by hand. The Jira timeline suits teams whose epics and dates are already tracked in Jira. Either way, the roadmap sits on a page with the context people need: goals, owners, what is out of scope and how to raise requests.
This guide shows how to set up that page in about a month, from gathering inputs to a regular review. It covers the exact steps in the macro, a page layout that answers stakeholder questions before they ask, a filled-in quarterly example, who owns updates and how to present the roadmap in a review. It assumes Confluence Cloud. Menus in Data Center differ slightly, so check your version's documentation.
The roadmap at a glance
Goal: A Confluence page holds the team's current quarterly roadmap with goals, a visual timeline linked to detail pages, named owners and a regular review routine. Duration: 6 weeks
Gather inputs (Week 1)
Collect what the roadmap must show before you open Confluence.
- List the goals for the next two or three quarters from the product strategy or OKRs.
- Collect the initiatives already planned, with a rough start, end and owner for each.
- Ask stakeholders what they need to see: dates, themes, dependencies or only priorities.
- Decide the time scale: weeks for a one-quarter delivery plan, months for a longer view.
Milestone: A short list of initiatives with owners and rough dates, and an agreed time scale, reviewed by the product lead.
Structure the page (Week 2)
Create a page layout that gives the roadmap its context.
- Create the page in the team space, either blank or from a roadmap template in the template browser.
- Add sections in this order: goals, the visual roadmap, now, next, later, out of scope, how to request changes.
- Add page properties at the top: owner, last reviewed date and next review date.
- Agree on a naming rule for the page, such as Product roadmap followed by the half year.
Milestone: The roadmap page published with every section and the owner shown at the top.
Build the visual timeline (Weeks 2-3)
Turn the initiative list into lanes, bars and markers.
- Insert the Roadmap planner macro by typing a slash and the macro name in the editor.
- Set the start and end dates and choose a weekly or monthly view.
- Add one lane per team, product area or theme, and give each a color.
- Add a bar per initiative, drag it to its dates and add a short description.
- Add markers for fixed dates such as a launch, a conference or a code freeze.
Milestone: Every initiative on the list appears as a bar with dates, and every fixed date appears as a marker.
Link details and Jira (Weeks 3-4)
Connect each bar to the detail people need, without crowding the roadmap.
- Link each bar to an existing page, such as a product requirements page, or create a new one from the bar.
- On each detail page, add the goal, scope, owner, Jira epic and open questions.
- If delivery dates live in Jira, embed the Jira timeline on a separate section or child page.
- Remove anything from the roadmap that is a task rather than an initiative.
Milestone: Every bar opens a detail page with an owner and a link to its Jira epic.
Review with stakeholders (Week 5)
Check the roadmap with the people who depend on it before calling it official.
- Share the page with engineering, design, sales, support and leadership leads.
- Hold a 30-minute walk-through and collect questions as inline comments on the page.
- Resolve each comment by changing the roadmap or answering in the thread.
- Agree on the next review date and record it in the page properties.
Milestone: All stakeholder comments resolved and the roadmap marked as approved by the product lead.
Set the update routine (Week 6)
Make sure the page stays current after launch.
- Set a recurring review, such as every two weeks for the product team and monthly for leadership.
- Add a short change log at the bottom: date, what changed and why.
- Use page version history to compare versions when someone asks what moved.
- Watch the page so owners get notifications when someone edits or comments.
Milestone: The first scheduled review held and logged, with the next date set.
How to build it with the Roadmap planner macro
The Roadmap planner is a built-in Confluence macro. You draw the roadmap directly on the page, which makes it fast for high-level plans that do not change every day. Here are the steps in Confluence Cloud.
The macro saves inside the page. It is not available in live docs at the time of writing, so if you work in a live doc, convert it to a page first from the More actions menu. Check Atlassian's documentation for the latest behavior.
- Open your page in edit mode, type a slash and start typing roadmap, then pick Roadmap planner.
- Select the roadmap and choose Edit to open the editor.
- Set the start and end dates and pick weeks or months for the timeline.
- Add lanes for teams, products or themes. Select a lane to rename it or change its color.
- Add bars for initiatives. Drag them into place, and drag either end to change the length.
- Select a bar to add a description, link it to an existing page or create a new page from it.
- Add markers for milestones and fixed dates, then publish or update the page.
Roadmap planner vs Jira timeline
Use the Roadmap planner when the roadmap is a communication tool: themes and initiatives over a quarter or a year, edited by one owner. It is quick to change and easy for non-technical readers. Its weakness is that it does not update itself. If dates change in Jira, someone must move the bars.
Use the Jira timeline macro when your epics and their dates already live in Jira and you want the page to show them as they are. It stays in sync, but it shows what Jira holds, which may be too detailed for leadership. Many teams use both: a Roadmap planner at the top of the page for the big picture, and an embedded Jira timeline lower down or on a child page for delivery detail.
Example: a quarterly roadmap for a B2B product team
Picture a product team at a B2B software company with three squads. The product lead builds the roadmap page for the next two quarters and sets the timeline to months.
Each bar links to a requirements page with the Jira epic. The page also lists two items that are out of scope this half, which saves many repeated questions from sales.
- Goals section: cut onboarding time for new accounts, and win larger customers with admin controls.
- Lane 1, Onboarding squad (blue): guided setup in Q1, data import from spreadsheets in Q2. Owner: onboarding product manager.
- Lane 2, Enterprise squad (purple): single sign-on and audit log in Q1, role permissions in Q2. Owner: enterprise product manager.
- Lane 3, Platform squad (gray): performance work across both quarters. Owner: engineering manager.
- Markers: annual customer conference mid-Q2, code freeze before the holiday period.
- Out of scope this half: mobile app redesign and a new reporting module.
Who owns what
A roadmap page goes stale when nobody owns it. Name one page owner and make each lane's owner responsible for their bars.
Show the owner and the last reviewed date at the top of the page. Readers trust a page they can see was checked last week.
- Product lead (page owner): structure, goals, final say on priorities, review schedule.
- Product managers (lane owners): bars, dates and detail pages for their area.
- Engineering managers: dependency and capacity checks, link to Jira epics.
- Stakeholder leads (sales, support, marketing): read, comment and raise requests through the agreed process.
How to present it to stakeholders
Present from the page itself rather than copying it into slides, so everyone sees the live version. Start with the goals section, then walk through the timeline lane by lane. Spend most of the time on what changed since the last review and why.
Leave task-level detail out of the meeting. If someone asks about a specific feature, open the linked detail page. Close with the out-of-scope list and how to request changes, so new ideas go into the right channel instead of becoming hallway promises. If leadership prefers slides, take a screenshot of the timeline and link back to the page.
How to adapt it
For a project roadmap rather than a product roadmap, use lanes for workstreams such as data, integration, training and cutover, and markers for go-live and key reviews. Link each bar to the workstream plan and the risk log.
For a large organization with many teams, give each team its own roadmap page and build a summary page for leadership with one lane per team and only the major initiatives. Keep the summary at the theme level so it does not need daily edits.
Common mistakes to avoid
- Putting every Jira ticket on the roadmap makes it unreadable, so keep the Roadmap planner at the initiative level and leave tasks in Jira.
- Building the timeline without context leaves readers guessing, so add goals, owners and an out-of-scope list on the same page.
- Letting bars drift from real dates destroys trust, so review the page on a fixed schedule and log each change.
- Hiding who owns the page means nobody updates it, so show the owner and last reviewed date at the top.
- Copying the roadmap into slides for every meeting creates conflicting versions, so present from the page and link to it.
- Using exact dates for work months away sets false expectations, so show later work in broader months or a later section.
Frequently asked questions
Does Confluence have a roadmap feature?
Yes. Confluence includes the Roadmap planner macro, which lets you draw lanes, bars and markers on a timeline inside a page. You can also embed a Jira timeline on a page with the Jira timeline macro.
How do I add a roadmap in Confluence?
Edit a page, type a slash and start typing roadmap, then choose Roadmap planner. Set the dates and scale, then add lanes, bars and markers. Publish or update the page when you are done.
Can I link a Confluence roadmap to Jira?
Yes, in two ways. Link each Roadmap planner bar to a detail page that references its Jira epic, or embed a Jira timeline with the Jira timeline macro so dates stay in sync with Jira.
Is there a roadmap template in Confluence?
Confluence's template browser includes roadmap-style templates, and more are available from the Atlassian Marketplace. You can also build your own page layout and save it as a template for your space.
How often should you update a Confluence roadmap?
A common rhythm is a team review every two weeks and a leadership review once a month or once a quarter. Record the last reviewed date on the page and keep a short change log.