Team Roadmap for Jira brings all of your Jira projects onto one clean, cross-project timeline — a holistic portfolio roadmap that is faster and easier to read than Jira’s built-in roadmap. Plan across projects, track progress and risk, capture baselines, forecast delivery, and share a read-only view with stakeholders, all without leaving Atlassian.
Open Team Roadmap from the Jira app navigation (the Apps menu). The main page shows your cross-project roadmap: rows of epics and initiatives on a timeline, each with its progress, target date and status.
The same roadmap is also available, read-only, as a Jira dashboard gadget and a Confluence macro, so you can place it where your team and leaders already work.
Each row represents a piece of work (typically an epic or initiative) and shows:
Click a row to expand the work beneath it. Click a ticket key to open its details.
Active and future sprints are drawn on the timeline so you can see what is scheduled and when.
Narrow the roadmap with:
Your filter, sort and theme choices are remembered per roadmap, so each roadmap reopens the way you left it. Switch between light and dark with the theme button next to the title.
Editable fields can be updated directly from a ticket’s details.
The Owner picker lists the people Jira says can be assigned the issue. Some fields may not be editable because Jira does not allow editing that field for the issue, screen, project or issue type. Team Roadmap follows Jira permissions and edit metadata — if you cannot change something in Jira, you cannot change it here.
Trend tiles summarise how each area’s completion is moving over time — up or down since the last period — so you can spot momentum and slippage at a glance without building a report.
A baseline is an on-demand snapshot of the plan.
Baselines are stored in Atlassian’s Forge app storage. They capture a compact summary of each item (key, target, progress) rather than full issue content.
When the roadmap projects a finish date for an area, you can commit the forecast — turn that projected date into committed target dates on the underlying tickets in a click. The change is written back to Jira as you, subject to your permissions.
If a Jira administrator has enabled it, you can ask the roadmap a plain-language question and get an answer drawn from your live roadmap.
The gadget and macro hide the editing and what-if controls, and they show each viewer only the work that viewer can already see in Jira.
Team Roadmap produces a weekly summary of what moved, what is newly at risk and what is overdue for a check-in, so teams get a regular pulse without opening the app. The digest is filtered to what each recipient can see.
Open the Team Roadmap settings admin page. Settings are shared across the whole site, so only a Jira administrator can change them.
Team Roadmap runs on Atlassian Forge. Jira data is requested using the current user’s Jira permissions.
The field may not be editable for that issue in Jira. Confirm the field is on the issue’s Edit screen and that you have permission to edit the issue.
Filters are remembered per roadmap in your browser. If browser storage is cleared or you open the roadmap in a different browser or profile, your saved choices will not carry over.
“Ask the roadmap” is off until a Jira administrator enables it in the Team Roadmap settings admin page.
Progress and dates are rolled up from the underlying Jira work and its target/date fields. Confirm the child issues and their dates are set in Jira, and that you have permission to see them.
The gadget and macro are read-only and show each viewer only the work they can already see in Jira. A viewer with narrower permissions sees less.