Jira Product Discovery Roadmap: Now, Next, Later Setup for Leadership

7 min read ยท 2026-11-15

A jira product discovery roadmap is a view of your ideas grouped by a Roadmap field (Now, Next, Later), with each idea linked to the delivery epics that build it. To set it up, add the Roadmap field, create a board view grouped by that field and connect each idea to its epics so progress updates by itself. You can then share the view as a live link or export a static image.

This guide is for product managers who present a roadmap to leadership, clients or other teams. It covers the Discovery side only. The dated timeline in a Jira Software project is built for delivery. Discovery works better when your readers need priorities and outcomes, and when anything after this quarter is still open. If your view already looks wrong, start with the next section.

The roadmap at a glance

Goal: A Now, Next, Later roadmap that the product team keeps current and that leadership can read without help. Duration: 2 weeks

  1. Decide what the roadmap must say (Days 1-2)

    Write down the message before you open Jira.

    • List two to four product goals for the coming quarters.
    • Group the work into three to five themes, one per goal.
    • Name your readers: leadership, clients, sales, the delivery team.
    • Agree on what "Now", "Next" and "Later" mean for your team. For example: Now is committed, Next is likely, Later is still being explored.

    Milestone: A short note with goals, themes, readers and the meaning of each column, approved by your manager.

  2. Set up the fields (Day 3)

    Every view depends on these fields.

    • Create a Roadmap select field with your options: Now, Next and Later. Add a Won't do option if you want to show what you dropped.
    • Create or reuse a Goal or Theme field so ideas can be grouped by outcome.
    • Add the fields leadership will care about, such as Impact or Customer segment. Keep the list short.

    Milestone: Every idea has a Roadmap value and a Goal value.

  3. Write ideas as outcomes (Week 1)

    An idea on the roadmap is a promise of value, not a feature spec.

    • Name each idea after its result: "Teams share one report" rather than "Dashboards v2".
    • Add one line about the problem and one about how you will know it worked.
    • Merge duplicates. A roadmap with forty cards tells readers nothing.

    Milestone: Each theme has a few clear ideas, and a client would understand every title.

  4. Build the board view (Week 1)

    In the left navigation, select Create a view, then choose a board.

    • Group the columns by the Roadmap field.
    • Sort the cards in each column by priority or impact.
    • Show only the fields a reader needs on the card: the goal now, and delivery progress later.
    • Create a second view, grouped by Goal, for your own prioritization work.

    Milestone: The board reads left to right as Now, Next, Later, and every card has a value.

  5. Link ideas to delivery (Week 2)

    This step keeps the roadmap honest.

    • Open each idea in Now, select the Delivery tab, then create a delivery ticket or add an existing epic.
    • In the delivery progress settings, choose how progress is counted: by issue count or by story points.
    • Add the Delivery progress or Delivery status field to the board so readers can see movement without opening Jira Software.

    Milestone: Every idea in Now is linked to at least one epic, and its progress bar moves as the team works.

  6. Share it with the people who read it (Week 2)

    You have two options, depending on your setup.

    • Live link: share or publish the view so readers always see the current version. Choose which fields they can see before you send it.
    • Static file: export the view as an image or a CSV, then put it in a slide or document. This works well for a board meeting or a client pack.

    Milestone: One reader outside the product team understands the roadmap without your help.

  7. Review and update (Every two weeks (suggested))

    Keep the shared roadmap in line with what the team is building.

    • Always move ideas between columns in Discovery first. Never change only the slide.
    • Move shipped ideas out of Now and into a column or view of recent launches.
    • In two or three lines, tell readers what changed since the last review.

    Milestone: The shared roadmap never contradicts what the team is building.

Why your Jira Product Discovery roadmap looks empty or wrong

Most of these problems come from the setup, not from a bug. Check these causes in order.

Fix the first two before anything else. They explain most empty boards.

  • No Roadmap field on the ideas: the board has nothing to group by. Create a select field (Now, Next, Later, or quarters) and fill it in on every idea.
  • The board is grouped by the wrong field: a board groups ideas by the field you choose. If it uses Status or Team, your Now, Next, Later columns never appear.
  • The timeline view has no dates to draw: the timeline places ideas on a monthly or quarterly scale. Ideas without start and end values don't appear on it.
  • A filter hides ideas: saved filters on a view are easy to forget. Clear them all, then add them back one at a time.
  • Delivery progress shows nothing: progress only appears when an idea is linked to a delivery ticket. Open the idea and use the Delivery tab.
  • Stakeholders can't open the link: your site admin must turn on publishing a view for people without a license, and it depends on your Jira Product Discovery plan. Check with your admin before you promise anyone a link.

Jira Product Discovery or the Jira Software timeline?

Choose based on the question your readers are asking.

Many teams use both. Discovery holds the "why" and the "what next". Each idea links to one or more epics, and the delivery team plans those epics in Jira Software.

  • Jira Software timeline: dated epics, sprints and dependencies. Best when the audience asks "when will it ship?" and the team works from the plan every day.
  • Jira Product Discovery: ideas, priorities and outcomes. Best when the audience asks "what are we working on, and why?" and any date after the current quarter would be a guess.

Jira Product Discovery roadmap example

Here is a short example for a B2B software team, grouped by the Roadmap field.

Leadership sees four cards, three goals and live progress on the work in Now. The engineers see the epics behind the first column.

  • Now: "New accounts reach their first report on day one" (goal: activation), linked to the guided setup epic. "Customers change plan without contacting support" (goal: retention), linked to the billing and account roles epics.
  • Next: "Managers share one report with their whole team" (goal: expansion). There is no epic yet, but the scope is agreed.
  • Later: "Data flows in from the tools customers already use" (goal: retention). This is still in research, with two integrations under review.

How to present a Jira Product Discovery roadmap to a client

Clients need less detail than leadership. Make a separate view instead of editing the internal one.

Before you send it, read it once as the client would. If a card needs explaining, rewrite its title.

  • Filter out internal ideas, code names and anything still under negotiation.
  • Show only Now and Next. Later invites requests you can't commit to yet.
  • Hide effort, scores and team names.
  • Add one sentence to each card about what the client will notice when it ships.
  • Say clearly that Next is a direction, not a commitment.

Common mistakes to avoid

  • If you use Now, Next, Later without defining the terms, people will argue about them later. Write the definitions on the view itself.
  • If you put every request in Later, the roadmap becomes a backlog. Only keep ideas there that you would actually defend.
  • If you share a view with every field visible, readers see scores and internal notes. Set the visible fields before you publish.
  • If the ideas in Now aren't linked to epics, nobody can see progress. Link the epic on the day work starts.
  • If you update the slide but not Discovery, you end up with two different versions. Change Discovery first and export again.

Frequently asked questions

Can I make a timeline roadmap in Jira Product Discovery?

Yes. The timeline view places ideas on a monthly or quarterly scale, and you can drag cards to another period. Use it when your readers need rough dates. Use the board when they need priorities.

Can people without a Jira license see the roadmap?

Often, yes, through a published view that gives them a read-only link. Your site admin must turn this on, and it depends on your plan, so check with your admin first. Anyone can open a static image export.

How do I connect a Discovery idea to a Jira epic?

Open the idea, go to the Delivery tab, then create a delivery ticket or add an existing one. One idea can link to several tickets, including tickets in different projects.

Should a Jira Product Discovery roadmap have dates?

Only where you can keep them. Many teams put dates on the current quarter and use Now, Next, Later for everything after it. A roadmap that keeps missing its dates loses its readers faster than one with no dates.

Generate this roadmap with AI