How can we help you?

What is RoadmapHero, in a nutshell?

RoadmapHero helps a team decide what to build, in what order and when — and keep everyone informed without endless meetings.

Everything your team wants to do is a ticket (an idea, a feature, a bug…). The same ticket then travels through the app, one page per step:

• Customer Voice: listen to what your customers say.
• Backlog: collect every idea in one place.
• Priorities: score ideas to decide what matters most.
• Planning: place the chosen work in time.
• Workflows: follow day-to-day progress on boards.
• Roadmap and Shared rooms: show the big picture to anyone, with a simple link.

Around this path, Strategy holds your vision and objectives, and Ask answers your questions about all this data.

How do I create my account?

Go to the Sign up page and choose:

• Sign up with Google, in one click, or
• your work email: you receive a verification code by email, then choose your name and a password (at least 8 characters, with an uppercase letter, a lowercase letter and a number).

Your workspace is then created automatically, named after your company’s email domain (you can rename it). Invited by a colleague? Click the link in the invitation email, choose your password and click Join the workspace: you land directly in their workspace.

You can also log in with Google or Microsoft from the login page.

What happens the first time I open the app?

A short welcome guide opens. It asks you one question, do you run products, projects or an organisation?, and prepares the right ticket types for you. From then on, the guide speaks your language: customers and releases for products, milestones and risks for projects, workstreams and decisions for an organisation. In six screens, it shows how the app works: customer voice, objectives and priorities, planning and roadmap, execution, a room per audience, and how stakeholders follow without you.

At the end you choose how to start:

• Start on an example: a complete example matching your answer, with objectives, six months of roadmap, feedback and shared rooms. Perfect to explore, and you can remove it in one click.
• Start on an empty workspace.
• Start from my own tickets: import them from Jira, GitHub or a CSV file.

The example depends on your answer:

• Products: "Fil Vert", a mobility app with its initiatives, epics, user stories and bugs, customer verbatims and weekly release notes.
• Projects: "Atlas", a CRM rollout across four branches, with its projects, tasks and requests, milestones, risks and deliverables.
• An organisation: "Cap 2027", a group’s strategic plan, with its workstreams, processes, decisions and risks, carried by several departments.

Want to see it again? Click your avatar at the bottom of the sidebar, then Getting started guide.

Which emails will I receive during my trial?

A handful, written by Laurent, the founder, and sent from his own address: reply and it lands in his inbox.

• When you finish the welcome guide: a welcome written for the way you work (products, projects or organisation), with the one piece of advice that saves the most time.
• Day 3: how to show your roadmap to the people who need it (leadership, sales, customers) with a shared page.
• Day 5: how to keep it up to date without effort: your workflow, the tools you connect (Jira, GitHub, Linear…) and your AI assistant.
• On the last day of your trial: what happens next, and how to keep going.

They follow the answer you gave in the welcome guide (products, projects or organisation), and they skip what you have already done: no day 3 email if you already share a page, for example. Once you subscribe, they stop.

Don’t want them? The Stop receiving these e-mails link at the bottom of each one stops the series; you keep the emails about your account and your tickets.

Joining a colleague’s workspace? You receive a single welcome email explaining where you are and where to start, and nothing more.

How do I find my way around the app?

Everything starts from the left sidebar:

• At the top, the name of your workspace (click it to switch workspace).
• In the middle, the main pages: Inbox, Strategy, Backlog, Priorities, Planning, Roadmap, Capacities, Workflows, Customer Voice, Shared rooms.
• At the bottom: Search (⌘K), Import tickets, What’s new (the latest changes, see below), Help (this page, which opens next to the sidebar), Settings, and your profile.

Ask is at the top right of each page, in the filter bar: it opens in a side panel, without leaving the page.

You can reorder the pages by drag and drop: your order is saved for you only. The small arrow next to the logo collapses the sidebar to gain space.

Some entries depend on your role: for example, Import tickets and Settings are only visible to owners and administrators (see roles).

The interface has changed: what is different?

Since late September 2026 the app is more contrasted and easier to read, with the same features:

• Every page with a side column (Inbox, Priorities, Workflows, Customer Voice, Sharing, Settings) now draws it the same way, with the page's name at the top.
• Filters, view switches and period selectors look alike from one screen to the next.
• Colour cues — ink, mint — point to what is selected or needs your attention.

If your account existed before the change, a short note presents it once. Tell us what you think from the chat: more subtle adjustments will follow.

Where can I see what’s new in RoadmapHero?

In What’s new, at the bottom of the left sidebar, just above Help. It opens next to the sidebar, like this help center.

Every release adds a few lines per change that matters to you: what you can now do, and where to click. The entries are grouped by month, newest first, and Learn more in Help leads to the full answer.

A number on What’s new tells you how many changes you haven’t seen yet (on a phone, a dot on the menu button). It goes away once you open the page, on all your devices; the changes you hadn’t seen keep a New for you mark until you leave it.

What the product already had when you created your account doesn’t count as new.

How do I quickly find a ticket or a piece of feedback?

Press ⌘K (Mac) or Ctrl K (Windows), or click Search in the sidebar. Type at least 3 characters: the search understands the meaning of your words, not just exact matches, in French and in English. "slow app" also finds "performance issues".

Before you type, your recent searches and a few examples are one click away. Results are grouped by kind — tickets, customer feedback, insights, opportunities, comments, objectives, key results… — and the chips at the top keep one kind only. Move with ↑ ↓, open with Enter, close with Esc. A button can even summarize the results with AI, citing its sources.

Search is available on computer, depending on your plan. On each page, the search box of the page filters by title.

Are there keyboard shortcuts?

Yes, a few that save a lot of time:

• ⌘K / Ctrl K: open the search.
• ← / → on the Roadmap and Planning pages: move to the previous or next period.
• ⌘ / Ctrl + Enter while hovering a Backlog row: add a new ticket right there.
• In any text editor: @ mentions a colleague, / opens the block menu (titles, lists, images…).
• On this help page: / puts the cursor in the search box.

How do I switch the app between French and English?

Open My profile (click your avatar at the bottom of the sidebar) and change the Language. The choice is saved for each workspace. Before you log in, the language is detected from your browser.

This help center has its own language switch, Français · English, at the very bottom of the page.

Can I use RoadmapHero on my phone?

Yes. On a phone, the pages are in a bar at the bottom of the screen, and your avatar opens a menu with your workspace, Import tickets, Help, Settings, Chat with us and log out (the chat bubble stays out of the way of the bar). Workflows lists its boards in a strip of pills at the top of the page. A text field opens the keyboard only when you tap it. You can also add the app to your home screen from your browser menu, to open it like a regular app.

The phone is perfect to check and update. For heavier work — planning, prioritizing, setting up — prefer a computer: the ⌘K search and the welcome guide are only available there.

I’m stuck. How do I reach support?

Click the chat bubble at the bottom right of the app (or the button at the bottom of this page) and write your question: a real person from the team answers. Response times depend on your plan (see plans).

This help center is always one click away: Help in the sidebar opens it right in the app, next to your pages.

What exactly is a ticket?

A ticket is one thing your team wants to do: a big initiative, a feature, a user story, a bug… It always has a type and a title, and can carry many details: description, dates, owner, priority, health, HeroScore, links to objectives and customers.

It’s always the same ticket you see in the Backlog, the Planning, the Roadmap, the boards and the shared rooms: change it in one place, it’s up to date everywhere.

What are ticket types and levels (epic, feature, story…)?

Each product has its own ticket types, organized in levels — from the most strategic (e.g. an initiative or an epic) to the most concrete (a story, a task, a bug). A big ticket can contain child tickets: in the Backlog they appear as a tree you can expand, and the Related tab of a ticket lists its children.

There are three levels: Strategic (e.g. an initiative), Build (an epic, a project, a process) and Delivery (a story, a task, a bug, a request…). When you create an item from the Backlog, the type menu lists them in that order, each under its heading, then Themes & releases at the bottom: themes and releases are not a level, they group tickets under a heading or a date. The current type is checked; only the levels you can create at that spot are shown.

Types are prepared by the welcome guide according to what you manage (products, projects or an organisation) and can be changed at any time in Settings → Products.

How do I create a ticket?

The fastest ways:

• In the Backlog, use the quick-add row, or hover a row and press ⌘ / Ctrl + Enter to insert a ticket right below it.
• From the Planning and Roadmap pages, when "Add tickets" is enabled in the display options.
• By asking Ask: "create a bug ticket for the login crash" — it proposes the ticket and waits for your confirmation.
• In bulk, with Import tickets (see the CSV import).

A title is enough to start: you can fill in the rest later.

Creating and editing tickets requires the Builder role or above (see roles).

How do I open a ticket, and send it to a colleague?

Click a ticket anywhere: it opens in a side panel, without leaving your page. Every field can be edited directly there.

To share it, click Copy link at the top of the ticket: the link opens the ticket’s full page for any member of your workspace. The same menu lets you duplicate the ticket, change its parent, archive or delete it.

What are the tabs of a ticket for?

Each tab follows one step of the ticket’s life:

• Content: the description (with templates and AI writing help), the comments and the activity log.
• Prioritize: what the ticket brings and what it costs — this is what builds its HeroScore (see how).
• Decisions: the decisions the ticket applies (see how).
• Build: the link with the code on GitHub or GitLab — branch, pull request (merge request on GitLab), issues, commits.
• Announce: the user-facing announcement and a short FAQ, shared automatically once the ticket ships.
• Customer voice: the customer feedback and opportunities linked to the ticket.
• Related: its child tickets (only when it has some).

A small check mark on a tab tells you it’s already filled in.

What do the fields on the right of a ticket mean?

At the top, the yellow Workflow note shows where the ticket stands in its workflow (the current step, who handles it, the estimate) and its two dates: Start and Roadmap (the date it should be available).

Below come the details:

• Priority: from P0 (critical) to P3 (low).
• Sizing: the size of the work, on your workspace’s scale (T-shirt, Fibonacci… see sizing).
• Health: on track, moved, paused, at risk or delayed — with an optional "why?".
• Owner, Version, Estimated date, Estimated cost and Actual cost, Main KPI.
• Tags and Teams, to sort and filter.
• Dependencies: blocked by / blocking other tickets.
• Notes: a private sticky note, flagged by an icon everywhere the ticket appears.
• Your workspace’s custom fields.

Too many fields? Configure fields lets you reorder or hide them — for you only.

How do I size a ticket (T-shirt, Fibonacci…)?

Open the ticket: in the right column, just under Priority, click Select a size and pick a value. No sizing clears it.

The scale is the same for the whole workspace. Choose it in Settings → Custom fields, on the Sizing row (button T-shirt · 2XS → 3XL):

• T-shirt: 2XS, XS, S, M, L, XL, 2XL, 3XL.
• Fibonacci: 0, 1, 2, 3, 5, 8, 13, 21 — like story points.
• Exponential: 0, 1, 2, 4, 8, 16, 32, 64.

These are the scales your workflow steps already use for their own estimates. Changing the scale keeps the sizes already set, even those outside the new scale.

With Jira or Azure DevOps: match Sizing with a field of the tool (in the integration’s Fields tab), such as Story points, a "T-shirt size" list or a text field. The size then syncs both ways. A T-shirt size is not sent to a number field, and a size the tool refuses never blocks the rest of the sync (title, description, dates).

In Capacities: map each size to man-days (and a cost) to estimate your tickets from their size — see how.

How do I link a ticket to an objective, a team or a customer?

In the side panel, just under the title, three rows tell who the ticket is for:

• Serves: the business goals it contributes to.
• Concerns: the internal teams (business units) it matters to.
• Engage: the customers, segments or customer statuses who asked for it.

These links feed the HeroScore, let you filter every page, and decide which shared rooms show the ticket — so each audience only sees what concerns it.

Why does an objective marked “Suggested” appear on my ticket?

When a ticket has no objective yet, the AI reads its title and description and, if one of your product’s objectives is an obvious fit, shows it in the Serves row marked Suggested.

• Click it to link the ticket to that objective, exactly as if you had picked it yourself (its children follow, as usual).
• Click − to hide it: no suggestion will come back on that ticket.

Nothing is ever linked without you. A title of a few words gets no suggestion: add a description, and the suggestion appears a few seconds later. A ticket that already has an objective, for instance from its parent, never gets one.

Suggestions are part of plans with AI prioritization. An agent connected through MCP can ask for the same suggestion with the `suggest_item_objectives` tool.

Can the AI help me write a ticket?

Yes. In the Content tab, click Help me to write… and choose:

• Le Génie — Structure my draft: turns a few messy notes into a clear ticket (context, objective, expected result).
• Jiminy — Generate specifications: writes the functional specifications from the ticket, its parent and child tickets, your objectives and vision.

You can ask it to start from what is already written, and add some context. The result appears as a draft: validate it to add it to the description, or throw it away. Nothing is saved without you.

You can also save a description as a template and reuse it on other tickets.

How do we discuss a ticket and keep track of decisions?

Under the description, the Comments area is where the discussion happens: reply, search, and @mention a colleague to notify them by email.

A comment can be flagged Bug report: it reports a problem, which can then be marked as solved.

Decisions have their own place: the ticket’s Decisions tab lists the decisions it applies, with an owner, a date and a status (see how).

Below, the Activity log keeps the full history: every field change, who made it and when, including automatic changes (imports, White Rabbit rescheduling…) and those of AI assistants connected through MCP, credited to their key (see MCP activity).

How do I announce a new feature to users?

Open the ticket’s Announce tab:

1. Click Write with Zazu: the Zazu agent drafts an introduction, the user benefits and the company benefits from the ticket description. Prefer your own words? Click Write it myself.
2. Add a video or an image at the top: paste a YouTube, Loom or Tella link, or click Add an image.
3. Optionally, write a short FAQ with Jiminy (this needs a GitHub pull request or a GitLab merge request linked to the ticket).

The head of the card presents Zazu: when it updates the announcement, and that your edits stay, with Rewrite with Zazu (starts over and replaces your edits), Set up Zazu (tone, length, publishing step) and See its activity.

Below come the title and introduction (click any text to edit it), the video or image, then User benefits and Company benefits side by side, Built by (add a builder, thank the team with the heart), the Frequently asked questions by Jiminy and the reader reactions. The ↻ button next to a part rewrites only that part. A padlock marks what customers never see in shared views: the company benefits and the builders.

You don’t even have to click: as soon as a ticket has a description, Zazu writes its announcement a few minutes after you stop editing, and updates it whenever the title or description changes — from the app or from your AI assistant through MCP. A part you rewrote yourself is never overwritten, and your pictures and video stay. Nothing is published before the ticket ships.

The announcement is then shared automatically in the shared views of the product and of the objectives, teams and customers linked to the ticket, where readers can react to it.

How do I show that a ticket is blocked by another one?

In the ticket’s Dependencies field, add the tickets it is blocked by (or those it is blocking). The link appears on both tickets, so the team sees at a glance what must be done first — and Ask can point out risky dependencies.

Should I archive or delete a ticket?

Archive, in most cases: the ticket leaves your views but keeps its history, and you can find it with the Archived filter of the Backlog and unarchive it. Delete is permanent and can disturb a planning that relied on it — a red banner at the top of the ticket asks you to confirm (Delete ticket, or Cancel / Escape).

Both actions exist on the ticket (top menu) and in the Backlog after selecting several tickets.

What is Customer Voice for?

Customer Voice turns scattered feedback into clear priorities, in three steps:

1. Customer messages: the raw feedback — a support ticket, a sales call note, a survey answer.
2. Insights: what the AI understood from each message — the theme, the tone, the emotion, whether it’s a pain point and whether it’s actionable.
3. Opportunities: improvement ideas that group many insights ("Make export easier to find — 14 mentions"), that you accept and link to tickets.

Customer Voice depends on your plan (Business and above).

How do I bring customer feedback into RoadmapHero?

Click Add Customer Messages in Customer Voice and choose:

• Create a message: type or paste one piece of feedback, with its source.
• Import CSV: up to 2,000 messages at once — an export of your support tool, a survey, a spreadsheet.
• MCP integration: let an AI assistant (Claude, ChatGPT, Cursor…) add messages for you (see MCP).

You can also ask Ask: "add this feedback from Acme: …". Each message is then analyzed automatically (status In queue, then Analyzed).

Adding messages requires the Builder role or above.

What do the four tabs of Customer Voice show?

• Opportunities (opened first): the improvement ideas to decide on. The line on top of the table gives their number, Columns, New opportunity and Detect opportunities; when the AI has suggested some you haven’t opened yet, a green strip above offers to Review them.
• Insights: everything the AI extracted, with theme, tone and emotion.
• Customer messages: the raw feedback, with its source, company and analysis status.
• Dashboard: the big picture — three figures (Insights, with how many are actionable, Positive feedback and Pain points), then two charts: Business health, the tone of your customers from detractor to promoter, and Emotions by theme. Click a slice or a segment to read the insights behind it. Below, Top pain points and Top opportunities rank the themes with the most negative feedback and the most actionable insights.

The tabs sit in the column on the left, which runs the full height of the page; the double arrow folds it down to its icons. In the bar beside it, at the top, filter everything by period, theme, product, company or status. The period is the dark chip: All time, the last 7 days, 30 days or 3 months, or a custom range.

On Insights, Customer messages and Opportunities, a second line under the filters holds two arrows, which scroll the table sideways when its columns don’t fit, and a search (Search the list…): it keeps the rows whose text, author, company or theme contains what you type.

What is an opportunity, and what do its statuses mean?

An opportunity is an improvement idea backed by real feedback. Its status tells where your decision stands:

• Suggested: detected by the AI, waiting for you.
• Accepted: worth acting on.
• Refused: you decided not to act — it’s a decision too.
• In progress: the work has started.
• Closed: handled.

From an opportunity, create a new ticket or link an existing one: the ticket’s Customer voice tab then shows the feedback behind it, and you know who to tell when it ships.

Why doesn’t an opportunity show up when I filter by company or product?

Because it isn’t linked to that company or product. With the default filters (every entry of Companies and Products selected), the Opportunities tab shows every opportunity, including those linked to no company or no product — for example one you created by hand.

As soon as you narrow Companies or Products, only the opportunities linked to your selection remain. An opportunity without a company then matches No company, like customer messages without a company. To see it again, select every entry of the filter, or link the company or product to the opportunity.

What is the number next to Customer Voice in the sidebar?

It counts the suggested opportunities you haven’t opened yet: new customer signals waiting for your review. Open them and the counter goes down.

What is the Backlog page for?

The Backlog is the list of all your tickets, organized as a tree: big tickets contain their child tickets, that you can expand or collapse (Expand all / Collapse all). It’s the page where you add ideas, clean up, reorder by drag and drop, and check that nothing is forgotten. To present it outside the product team, switch to a simpler view (see the views).

A good routine: drop every new idea in the Backlog, then sort it once a week — clarify, score, plan or archive.

Can I show the Backlog more simply, for example to present it to my organization?

Yes: use the view switch at the right of the filter bar. Besides the usual Tree, two views show the Backlog at the initiative level, without the technical detail:

• Overview: the initiatives in panels, one line each, showing its available date and the share of its tickets already delivered, as a percentage coloured by stage (grey: up next, orange: in progress, green: delivered). Click an initiative to see what it holds (Related tab). Group by makes one panel per Theme, Business objective, Business unit, Customer or Segment (with its icon, or the customer's logo taken from its domain), or a single panel — an initiative linked to two objectives shows under both. Sub-levels lists, under each initiative, the tickets it holds (features, stories…). A panel's 2 delayed tickets (or at-risk) figure counts the tickets whose health says so: click it to see which ones and open them.
• Grouped by Theme: New theme (top right) creates a theme, and each theme's Add button creates an item in it — an initiative unless you pick another Ticket type — or files an existing one there. Drag an initiative onto another theme to move it, and drag a theme by its handle to reorder the themes.
• Map: the product as a whiteboard diagram — the product, its themes (or objectives, business units, customers, segments), their initiatives and, with Sub-levels, the tickets they hold, all joined together. An icon shows each item's stage (empty: up next, half: in progress, check: delivered). Grouped by business objective, Key Results also shows each objective's KRs and their progress. Drag the background to move around and an item to arrange it (its branch follows); Re-align puts everything back. The + that appears on the edge of an item (product, theme, initiative…) creates an item under it: pick the Ticket type — the next level down is preselected, a Theme under the product, an Initiative under a theme — then type its title and press Enter (more). Grouped by business objective, business unit, customer or segment, a dashed column at the end creates one more, and the + of an objective creates a key result under it (how). Pinch or use Ctrl + wheel to zoom. The map opens at a readable zoom, centred on the product; Fit to screen shows it all.

Tickets that belong to no initiative are not shown as initiatives: they are gathered under Other tickets, listed on demand. Initiatives placed outside any theme appear under No theme.

An initiative is in progress as soon as one of its tickets is in progress or delivered, and delivered once all of them are. Filters and search apply to every view, and the Backlog remembers the view you picked. Until you pick one, it opens on the Tree, or on the Map for a product set up to run your organisation (why).

The eye icon (display options) has its own settings in these views: type icon, ID, stage, progress, owner, available date, health alerts and status color.

Why does my Backlog open on the Map instead of the Tree?

Because the product is set up to run your organisation (the choice made in the welcome guide or in the product's setup: Manage your products, Manage your projects or Run your organisation). An organisation reads its backlog as a whole — themes, initiatives and how far along they are — so its Backlog opens on the Map. Products and projects open on the Tree.

It is only the starting point: pick another view in the view switch at the right of the filter bar and the Backlog remembers it the next time, whatever the product.

When I click a + on the Map, can I choose the type of ticket I create?

Yes, always. Every + of the Map (and the Add button of a theme in the Overview) opens a small Create: … box with a Ticket type choice: every type your product uses below that item. The next level down is preselected — a Theme under the product, an Initiative under a theme, the level below under an initiative — so a title and Enter are enough in most cases; click another type to create something else (a release, an epic, a task…).

The level that groups your initiatives is called Theme everywhere in the app, unless you renamed that type in Settings → Products.

Can I create an objective, a key result, a business unit, a customer or a segment from the Map?

Yes, if you are an owner or an administrator (see roles). Group the Map by what you want to create:

• Business objective: the dashed New business objective column, after the last objective, creates an objective (on all your products, as by default in Strategy → Manage objectives). The + that appears on the edge of an objective creates a New key result under it; the Key Results are then shown.
• Business unit, Customer or Segment: the dashed New business unit, New customer or New segment column creates one.

Type its name (or the key result's title) and press Enter. The new column shows at once, even before any initiative is linked to it, and the other screens (Strategy, Settings, ticket menus) list it too. To link an initiative to it, open the initiative.

Builders and contributors don't see these buttons. Key results need the Vision & OKR feature of your plan; if your plan doesn't include business units or customers, the dashed column opens the plans.

What do the numbers at the top of the Backlog mean?

The metrics bar is a health check of your backlog:

• The number of tickets, and how it changed over the last 30 days.
• The average age of tickets.
• The share of tickets already planned (with a start and a roadmap date).
• The median HeroScore, the typical priority level.
• Warnings, only when there is something to see: tickets with no owner, unplanned, delayed, at risk, stale (not updated for 30 days).
• One chip per ticket type.

Click a warning or a type to filter the list instantly, click again to clear the filter.

When the figures don’t all fit, arrows on the sides of the bar bring the others into view. Don’t need the bar? See how to hide it.

How do I hide the KPI bar at the top of the Backlog?

Open the Display menu (the eye, at the left of the filter bar) and untick KPI bar. The Backlog remembers it, in every view; tick it again to bring the bar back. A warning filter picked from the bar is cleared when you hide it.

How do I filter the list and save my favorite filters?

Use the filter bar above the list: product, type, status, health, business goal, business unit, customer, tag, team, owner, assignee… Advanced filters add priority, HeroScore, version, dates, costs and your custom fields. The search box finds a ticket by its title. In the Types filter, the initiative level shows a padlock and Always shown: it cannot be unticked, since the rest of the backlog is read through it.

Found the right combination? Open Favorite filters and save it as a view: it’s one click away next time. Your favorite filters are personal, and also exist on the Planning, Roadmap and Workflows pages.

Can I choose what each row displays?

Yes: click the eye icon (display options) and show or hide the ticket number, status, subscribers, health, dates, drivers, owner, priority… The status color option tints rows green once delivered and amber while in progress — handy to spot at a glance what moves.

How do I change many tickets at once?

Tick the tickets (or Select all), then choose an action in the bar that appears: change product, change type, change parent, change health, archive or delete. Perfect to clean up an old backlog in a few minutes.

What is the HeroScore, and how is it calculated?

The HeroScore is a score from 1 to 5 stars (by default) that answers one question: is this ticket worth doing now? It weighs two sides:

• Impact — what the ticket brings: its impact on your business goals, on your business units and on your customers.
• Effort — what it costs: the effort to build, the effort to maintain, and your uncertainty about all this.

Lots of impact for little effort gives a high score: do it soon. Little impact or a huge effort gives a low score: it can wait.

The more links a ticket has (objectives, customers, teams), the more meaningful its HeroScore. A ticket linked to nothing scores low — that’s often a sign it deserves a second look.

How do I score a ticket?

Open the ticket and go to the Prioritize tab:

1. For each linked business goal, choose the impact: critical, high, medium or low.
2. For each customer or segment: blocking, essential, valuable or minor. For each business unit: must have, should have, could have or won’t have.
3. In Effort, set the uncertainty (0 to 100 %), the effort to build and the effort to maintain (light, low, mid, high, heavy).
4. Optionally, write a note to explain your reasoning to the team.

The HeroScore updates right away at the top of the tab. On big tickets, a switch can apply the same settings to child tickets.

Don’t aim for precision: the goal is to compare tickets with each other, not to predict the future.

What does the Priorities page show?

Two complementary views, chosen in the left panel — at its top, a switch picks the kind of audience by its icon (business goals, business units, segments, customers):

• All tickets: how your HeroScores are distributed, and your tickets sorted from the highest score down — your natural to-do order.
• One business goal, business unit, segment or customer: at the top, its name, how many tickets it prioritized and how its asks split across the priority levels; the arrows next to it move to the previous or next one. Then an alignment matrix that crosses the HeroScore with the priority this audience gives to each ticket. Below, each ticket keeps its dates, its status and that priority, which you can change right there.

The matrix reveals four situations: aligned · do now (valuable and asked for), aligned · low priority, strategic blind spots (valuable but nobody asks — explain why it matters) and pet features (asked for but little value — discuss before committing).

Can I adapt the HeroScore to what matters for my company?

Yes, product by product, in Settings → Prioritization (administrators, depending on your plan):

• Choose the scale: 5, 10 or 100.
• Give each element a weight from "off" to ×10: each business goal, each business unit, each customer segment or status, and the execution factors (uncertainty, efforts). For example, give ×3 to your "Reduce churn" goal this quarter.

Then click Update HeroScore for all existing tickets to recalculate the whole product with the new weights.

Do I have to score every ticket?

No. Score what you’re seriously considering for the coming months. A good habit: as soon as an idea is discussed for real, link it to its objectives and customers and set its efforts. The Backlog shows the median HeroScore, so you can see whether your scoring keeps up.

Votes left by readers of your shared rooms also appear in the Prioritize tab: a concrete signal of demand.

What is the Strategy page for?

Strategy (in the sidebar) is where your vision and your objectives live, with their progress:

• The column on the left, always in view, starts with your vision, which sets the course for everyone — the AI can even generate a first draft for you. Under its answers, Detailed strategy opens the document that develops it. Your objectives, business teams, customers and segments follow, folded: click one to open it. Hover a name cut short to read it in full.
• Tiles summarize your objectives: running, on track, at risk, completed, upcoming.
• Your objectives and their key results are shown as a timeline, cards or a list, filterable by product. On the timeline, each objective names the products it serves under its title.

This page depends on your plan (Pro and above).

What are objectives and key results (OKRs)?

An objective is an outcome your company wants, in plain words: "Reduce churn". A key result makes it measurable: a metric, a target, a unit and a period — "Monthly churn under 2% by the end of Q4".

You then link tickets to the objective: everyone sees why a piece of work matters, and the HeroScore takes it into account.

How do I create an objective and its key results?

1. Open Strategy → Manage objectives (or Settings → Business goals) and create the objective.
2. Add a key result (New key result): title, description, metric, target and unit. The grey column of the window names the objective and ticks what a good key result has — a metric, a target, a period — as you fill them in.
3. Choose its period: a quarter in one click, six months, or your own dates, then Create key result (or Ctrl / ⌘ + Enter).
4. Link tickets to the objective, from the ticket (Serves row) or from the objective.

To delete a key result, click the bin on its line or on its page: a red banner opens in the key result itself, with Cancel and Delete key result — its contributions are lost.

You can also create objectives and key results from the Backlog Map grouped by business objective (how).

How is the progress of a key result calculated?

Each ticket that contributes to a key result gets two values: an estimated contribution (what you expect) and a realized one (what it actually delivered). Progress = realized total ÷ target. The app also tells you how much of the target your estimates cover.

The status is then automatic:

• On track: progress keeps pace with the time elapsed in the period.
• At risk: progress is falling behind the calendar.
• Achieved: 100 % reached. Upcoming: the period hasn’t started.
• After the end date: not achieved, above or below 70 %.

An objective’s progress is the average of its running key results. A progress analysis by the AI can summarize the situation of each key result (depending on your plan).

What are business units, customers and segments for?

They describe who you work for, and are managed in the Settings tabs of the same name (you can also create them from the Backlog Map, see how):

• Business units: your internal stakeholders — Sales, Support, Marketing…
• Customers: the companies or people who use your product, grouped into segments (e.g. "SMB", "Enterprise") and statuses (prospect, active, churner, lost).

Link them to tickets to weigh the HeroScore, to measure alignment on the Priorities page, and to give each of them a shared room showing only what concerns them.

These words don’t fit your company? Rename them everywhere in Settings → Custom wordings (e.g. "Departments" instead of "Business units").

How do I record a decision, and who can settle it?

Open Decisions in the sidebar, then New decision, the first row of the list. The form asks for what is decided and why, who it is owned by (a member of the workspace) and its status, the date from which it applies (shortcuts: Today, 1st of next month, Next quarter) and until when if it ends, then its scope: the products it concerns (+ Add a product, as on a ticket), what it is attached to (an objective, a business unit, a customer, a segment, or nothing), the business units and objectives impacted. Under To go further: the options rejected, the tickets that apply it and Confidential. The column on the left ticks what a clear decision has as you fill it in.

Click a decision to read it in a side panel: edit it with the pencil, delete it with the bin. To change its status, click it, in the list or at the top of the panel.

Dropping or stopping a decision In force asks why: the reason shows at the top of its panel and in its activity.

Its status follows a workflow: Proposed, Under discussion, Approved, In force, Ended, Dropped. Only its owner or an administrator can move it to Approved; then its dates do the rest: In force from its application date, Ended after its end date. Owners and administrators can rename, reorder or add statuses with the settings button next to New decision.

Filter the list by status, Products, Owned by, Business units and Objectives (impacted or attached), or search its text. The tiles at the top count what is In force, To settle, Upcoming and Ending within 30 days among them; click one to filter. Contributors read decisions without editing them.

To see decided decisions on the timeline, turn on Decisions in the Display menu of the Roadmap or the Planning: each one appears at its application date, for the products shown.

AI agents connected through the MCP can list decisions, propose one and link tickets to it, but never decide: that stays with the person who owns it.

How do I share decisions, and who sees which ones?

In Shared rooms, open a room and turn on the Decisions tab under What … sees. Its audience then sees the decided decisions (Approved, In force, Ended) that concern it, and only those:

• a room for a product: the decisions of that product;
• a room for a business unit: the decisions that impact it or are attached to it;
• a room for an objective: the decisions that impact it or are attached to it;
• a room for a customer or a segment: the decisions attached to it;
• the workspace room: every decision.

Each one shows its status, its dates and its why. Who owns it and the options rejected are never shown, and decisions marked Confidential are never shared.

Where are the comments I marked « Decision » on a ticket?

In the ticket’s Decisions tab. It shows the decisions the ticket applies (Link a decision or New decision to add one) and, under Comments marked « Decision », those noted before decisions existed. Promote to decision turns one into a real decision, prefilled with its text and its author, linked to the ticket. Nothing is deleted.

Comments no longer carry a « Decision » flag: create the decision from the tab instead.

What is the Planning page for?

Planning is your working timeline: each ticket is a bar that goes from its start date to its roadmap date. On the left, the Unplanned panel lists the tickets that don’t have dates yet.

Zoom from the day to three years (week, month, quarter, "months & quarters"…), move in time with the arrows or the ← / → keys, and come back to today in one click.

How do I plan a ticket?

Drag it from the Unplanned panel and drop it on the period of your choice: it gets its dates. Drag it back to Unplanned to remove them.

You can also set the Start and Roadmap dates directly on the ticket, in the yellow Workflow note (Plan button).

A ticket whose roadmap date has passed without being done can be rescheduled automatically by the White Rabbit agent, so your roadmap is never silently late (see the agents).

Can I create a ticket straight from the Planning or the Roadmap?

Yes. Hover a period, a release, a block or an initiative and click its +: the same new-ticket line as in the Backlog opens.

• Click the type to pick another one in the Backlog's type menu: every type allowed there, grouped by level. On a roadmap showing several products, choose the product the same way.
• Type the title and press Enter — Esc cancels.

A ticket created from a period gets that period's dates; created from a release or an initiative, it goes under it.

What can I display on the Planning?

The display options add useful layers:

• Themes and Releases: your themes and your releases become lanes that group their tickets.
• OKR: your objectives’ timeline above the tickets.
• On each bar: ticket number, HeroScore, priority, health, estimated or actual cost, type icon, status.

Sort by HeroScore, priority or backlog order, filter as everywhere else, and save your favorite filters.

What is a release?

A release is a named delivery that groups tickets shipped together — "v2.0", "Summer launch". In RoadmapHero it’s a ticket type flagged as a release in Settings → Products: put tickets under it as children, and it appears as its own lane on the Planning and the Roadmap.

How do I know if my team is overloaded?

Open the Capacities page. Month by month (or quarter by quarter), it compares your team’s maximum capacity with the work allocated to your planned tickets — and, once work is done, the time actually spent, measured from your workflows.

• Count in man-days or in euros, or look at the tickets’ Sizing: switch in the Capacities & costs panel on the left (View), where you also set the Default rate, then if needed a rate per workflow step or per person (optional, folded while empty) — right in the panel, each field saves on its own.
• Look at the whole team, by workflow step or by person.
• Move through the months with the arrows under the filters; Today brings you back to the current month. The search next to them narrows the grid to the matching initiatives.
• Each initiative shows its planned period on two lines, like a backlog row: the start, then → the end — click one to change it. The eye (Display) shows or hides the Dates and Status columns.
• The page opens on the product you last chose. With no product yet, it says so; if loading fails, a Retry button reloads it.
• Overcapacity and overcost warnings show where to act: move a ticket, reduce the scope, or add hands.
• New to the page? The panel’s How it works explains the three steps (estimate, spread, set the max) and its Legend reads the grid: hatched cells are outside the planned dates, red ones over the max capacity. Fold the panel to keep only the view switch.

Capacities depend on your plan (Business and above). For sprint-level capacity, see sprints.

How do I turn my ticket sizes (T-shirt, story points…) into man-days or a cost?

On the Capacities page, the Capacities & costs panel has a Size mapping table: for each size of your scale (S, M, L… or 1, 2, 3, 5, 8…), enter the Days it stands for and, if you wish, its Cost. Each field saves on its own; empty it to remove the size.

From then on, a ticket with a size and no estimate of its own is estimated from this table, and so is each workflow step with a size: its days count in the Total column, cap what can be spread over the months, and its cost appears in the Euros view (else its days × the rate). An estimate you enter by hand always wins.

To see the sizes themselves, pick Sizing in the panel (View), then:

• Global: the size of each ticket, with ≈ the man-days it stands for.
• By step: the size of each workflow step of the ticket (steps sized in hours or days show their duration).

In this view, the months show sizes, not man-days: each ticket’s size (or its steps’ sizes) on every month its dates cover, and on top, the Planned sizes of each month: T-shirt sizes counted (M ×2 · L), points, days and hours added up.

Click a size to change it right there: it is the ticket’s own Sizing field, so a ticket matched with Jira or Azure DevOps syncs its new size.

When your workflow steps use another scale than your tickets, the table shows one tab per scale. Costs need the euro view, depending on your plan.

Can I export my planning or my roadmap as an image?

Yes: use Export as image on the Planning or Roadmap page. You get a PNG of what’s on screen (with your filters, up to 6 columns), ready to paste in a slide or an email.

Better than an image that gets outdated: a shared room always shows the up-to-date version.

What is a workflow, and what is a pipeline?

A workflow is the path a type of ticket follows from idea to delivery. It’s made of one or more pipelines — for example "Discovery", then "Development", then "Rollout" — and each pipeline has its steps (the columns of its board).

The workflow is split in two around the roadmap date: the pipelines before it prepare the work, those after it deliver and roll it out. Each ticket type has its own workflow, set in Settings → Workflows.

Which boards can I open in Workflows?

The left panel of the Workflows page lists:

• Overview: all your products at once, one column per pipeline — perfect for a weekly review.
• One board per pipeline, grouped before / after the roadmap date, with one column per step.
• No workflow: a simple open / closed board for tickets that don’t follow any workflow.

To see one person’s work, filter by assignee. Date filters ("done in the last 7 days", "starting this week"…) help prepare your rituals.

How do I move a ticket forward?

Drag its card to the next column: its step changes immediately, everywhere in the app. New tickets arrive in the Incoming column. A ticket you give up on can be dropped in the Aborted zone — and put back in the flow later if needed.

Each step of the workflow can have its own assignee and estimate, visible in the yellow note of the ticket.

How do sprints (cycles) work?

On a pipeline board, create a sprint with New Sprint: name, start and end dates, capacity (in points, days or hours, depending on your sizing scale), goals, and optionally a capacity per person.

1. Fill the sprint by hand, or click Fill my cycle: it adds sized tickets that aren’t done yet, the most urgent first (nearest end date), until the capacity is reached.
2. The sprint locks automatically on its start date (you can also lock or unlock it yourself).
3. At the end, Complete Sprint shows the stats and moves the unfinished tickets.

Sprints depend on your plan. Past sprints stay available from the board.

Can a ticket be handed to Claude automatically?

Yes. Mark a step of your workflow as a Claude step: every ticket that enters it is sent to Claude Code with its full context (description, objectives, stakeholders, customers). Claude does the work with your Claude account and your connectors (pull request, document, analysis…) and reports back on the ticket.

To set it up, open Settings → Agents → Claude and follow the 4 steps:

1. Add the RoadmapHero connector in Claude, with a key that can Create and edit (see the MCP server).
2. Create a scheduled task in Claude Code, paste the prompt shown, and add an API trigger.
3. Paste its Fire URL and its token, then click Test.
4. Turn on Claude step on the right column: in that screen, or straight on a work status in Settings → Workflows (the Claude switch next to its name).

When Claude is done, the ticket moves to the next step (for example To test) and its Build tab shows Claude’s result: a summary, the deliverables (pull request, documents) and Open the session. If Claude has a question, the ticket goes back to the previous step with the question. Write your remark or answer and click Send back to Claude.

On the board, a Claude column carries the Claude mark, and each card handed to Claude shows its state (working, result to review, question, error). Claude also writes in the Inbox when it is done, has a question or could not start, and when it has not reported after a day.

Each ticket starts one Claude session and counts toward your Claude usage (30 launches an hour at most). Nothing runs on RoadmapHero’s side.

How do I change the columns (steps) of my boards?

In Settings → Workflows (administrators): pick a ticket type, then add, rename, reorder or remove its pipelines and their steps. Boards update right away.

Keep it simple: 3 to 6 steps per pipeline are enough for most teams. Too many columns slow everyone down.

What is the difference between the Roadmap and the Planning?

They show the same tickets, for two different audiences:

• The Planning is the team’s working tool: exact dates, bars, unplanned tickets to place.
• The Roadmap is the communication tool: tickets grouped by product, with your releases, themes and objectives in lanes, and a clear color code — green when done, yellow in progress, white to come.

The Roadmap is the view you open in a steering meeting, and the one you share.

Can I show a roadmap without precise dates (Now / Next / Later)?

Yes. In the time scale selector, choose Now / Next / Later: tickets are placed in three horizons instead of on dates.

• Now: what the team is working on.
• Next: what comes right after.
• Later: what’s on the radar, without commitment.

It avoids promising dates you can’t hold. By default the horizons are 3, 6 and 9 months; change them in Settings → Agents → White Rabbit.

How do I adjust what the Roadmap shows?

Three tools, at the top of the page:

• The time scale: week, month, quarter, year, "months & quarters" or Now / Next / Later.
• The filters: product, type, status, health, objective, business unit, customer, tag, team, owner — and your favorite filters.
• The display options, sorted in three groups: On the roadmap (OKR, themes, releases, add tickets), On the cards (full titles, what's new, end date, type icon, priority, status, tags) and Costs.

Preparing a roadmap for a specific audience? Filter it, then share it through a shared room rather than a screenshot.

How do I change the colour of an initiative?

Open the initiative and click the coloured square next to its title. Pick one of the 88 colours: 22 hues (from rose to slate), each in four tones — Soft, Light, Medium and Deep. The colour follows the initiative on the Roadmap, the Planning, the Backlog and the shared rooms.

• Every colour stays readable under the text of the card, even the deepest.
• A new initiative (created by hand, by an agent or imported from Jira, GitHub or Productboard) gets a light or medium colour at random: change it whenever you like.
• An initiative coloured before this palette keeps its colour: the picker shows it as the Current colour until you choose another.

The frame of the Roadmap and the Planning (period headers, columns, drop zones) stays sober on purpose, so your initiatives' colours stand out.

What does the blue “New” on the edge of a card mean?

The ticket is New: it was put on the roadmap recently. The word New, in blue, sits on the top edge of its card, on the right; hover it to see the date the ticket was planned. Initiatives heading a column don’t carry it: their tickets do. To turn it off, untick Display → What's new; in a shared room, it is the What's new element.

By default a ticket shows it for 7 days. Change the duration — or the date from which tickets can show it — in Settings → Agents → White Rabbit.

Why doesn’t my ticket appear on the Roadmap?

The usual reasons, in order:

1. It has no dates yet: plan it first (see how).
2. Its dates fall outside the visible period: move in time with ← / → or zoom out.
3. A filter hides it: check the filter bar, or clear it.
4. It is archived.

How do I share my roadmap with people who don’t have an account?

With a shared room: a read-only page, always up to date, that you send as a simple link. No account is needed to open it.

1. Open Shared rooms in the sidebar.
2. Choose the room in the column on the left: pick its kind by its icon — a product, a business goal, a business unit, a customer, a segment or a customer status — then the room itself.
3. Choose what it shows (see what a room contains).
4. Open Share and turn on the Link: copy it and send it.

Each audience only sees the tickets linked to it: the Support room shows what is done for Support, the Acme room what is done for Acme.

What can a shared room show?

Under What … sees, you turn on the tabs: Strategy (vision and objectives, laid out as on your Strategy page), Roadmap, Planning, Backlog, Decisions (only those that concern the room’s audience, see how) and Release notes. Then, under Customize for …, the details:

• On tickets: business changelog, insights, description, prioritization.
• Display: title, priority, status, type icon, sort order, period.
• Filters: types, statuses, objectives, tags, teams, HeroScore…
• On its own line below: how many months before and after today the roadmap and the planning show — click a figure to change it.

Visitors can vote for a ticket, subscribe to be notified when it moves, and — depending on your plan — search the room or ask questions to an AI that only answers from what you shared.

Can the news go out by itself (email, Slack, Teams…)?

Yes — that’s the point: your stakeholders follow without you. From the Share window of a room, besides the link:

• Embed the room in another tool (intranet, wiki…).
• Post it in Slack, Microsoft Teams, Discord or Notion.
• Send it by email to a list of recipients, at the frequency of your choice, with live notifications (each ticket delivered, weekly release note).

To write a newsletter, see Generate a newsletter.

Automatic channels depend on your plan.

How do I publish a “What’s new” page for my own users?

Open Shared rooms, then What’s new at the top of the column on the left, under For the whole workspace.

1. Each time an item of your roadmap moves to Done (green), we write a short update for your users from its description, its changelog and its linked pull requests. What users would never notice (refactoring, dependencies, tests…) goes to Set aside.
2. In Content, read the updates in To review: Edit the title, the text, the kind (New, Improvement, Fix) or the date, then Publish. Add writes one by hand. Publish without review, at the top, sends updates out as soon as they are written.
3. In Appearance, choose your color, the Heading typeface and the Text typeface, and show your workspace’s logo (added in Settings → Workspace → Customization, see how). In Settings, give the page its title and subtitle in each language. Under Page languages, keep French and English together: each update is then written in both, and your users switch from one to the other at the top of the page. An update written in one language only (an older one, or one you add by hand) is translated automatically; if one still lacks a language, Translate into English (or into French) writes it in one click.
4. Turn on the Public link, then Copy the link to send it, Open the page, or copy the Embed code to show the page on your website or help center.

The tabs (Content, Appearance, Settings) sit on the left and the preview on the right, so you see each change as you make it. The preview is exactly what your users see: published updates only, in the language you pick above it. An update can only be published once it is written in every language of the page.

The first time, the page is prepared from the items that moved to Done over the last 90 days. Turning the link off and on again gives it a new address.

How do I generate a newsletter of what we delivered?

Open Shared rooms, then Generate a newsletter at the top of the column on the left.

It goes in three steps, shown at the top:

1. Scope: choose who it is for: The whole workspace, A product, A business goal, A business unit, A customer, A segment or A customer status. Except for the whole workspace, pick which one right below (Which product?…). Then Continue.
2. Content: click a period (Last 30 days, Last month… or your own dates), the ticket types and the statuses to include. Ticket types are grouped by level, as when you create a ticket in the backlog (Strategic, Build, Delivery, Themes & releases): click a level’s name to take all its types at once, or click the types one by one. The number of tickets that will go in shows next to Generate newsletter.
3. Newsletter: edit the text, then Copy HTML and paste it in your emailing tool. Regenerate writes it again.

Click a completed step to go back to it: your choices and your newsletter are kept. The newsletter isn’t saved: copy it before leaving.

How do I pick the Slack channel and see what the message will look like?

In the Share window of a room, turn on Slack and pick your Slack workspace. Then click the Channel field: type a few letters in Search a channel to find it quickly.

A private channel only shows up once the RoadmapHero app has been invited to it.

In the Preview in Slack box below the message, Send a test posts it once, right now, in the chosen channel, with its link and a line saying it is a test. Open Slack to see exactly what your team will receive. The schedule doesn’t change.

Is a shared link safe? How do I stop sharing?

The link contains a unique, unguessable key: only people who received it can open the room, and they can’t change anything. There is no password, so share it with the right people — like any link.

To stop sharing, open Share and turn off the Link (or Embed) switch: the page immediately shows "This shared view is no longer available". Turn it back on whenever you want.

Do I need to re-send the link when things change?

No. A shared room always shows the current state of your data: change a date, deliver a ticket, and visitors see it next time they open the link. That’s the big difference with a slide or an exported image.

What can I ask Ask?

Ask is an assistant that knows your workspace: tickets, objectives and key results, workflows, customer feedback and insights. Ask in plain words:

• "Which tickets are at risk this quarter?"
• "Summarize what customers say about the export."
• "Which key results are behind, and why?"

Ask can also act for you — create a ticket, change a status, add a customer message, update a key result — but always as a proposed action you must confirm.

Click Ask at the top right of any page, in the filter bar: it opens in a side panel, so you can ask about what you are looking at. Conversations, at the top of the panel, lists your past conversations; the pen starts a new one. A click elsewhere on the page closes the panel, and what you were typing is still there when you open it again. The arrow icon opens Ask in full page, and the full page can be reduced back to the panel.

Ask only sees your current workspace. It is young and still learning: double-check important figures before a big decision.

Who can see my Ask conversations?

Conversations are shared with the whole workspace, so a good analysis benefits everyone. The side panel lists them by date; search them, filter on my conversations, pin the useful ones and archive the others. Only the author (or an administrator) can delete a conversation.

At the end of a conversation, rate it from 0 to 10 and leave a comment: it directly helps improve Ask.

Is there a limit to the number of Ask messages?

Yes, a daily limit per person and per workspace, which depends on your plan. When it’s reached, a message tells you so: Ask is available again the next day.

Who are the agents (Baymax, Jiminy, Zazu, White Rabbit, Claude…)?

Each agent takes on one job of your product routine. Find them all in Settings → Agents: each row names the subject the agent handles, with the agent’s name beside it.

• Baymax analyses your customer feedback and turns it into insights and opportunities.
• Le Génie tidies up a messy draft into a clean ticket.
• Jiminy writes functional specifications, and the FAQ of a feature.
• White Rabbit keeps your dates up to date by moving overdue tickets.
• Tic & Tac link your GitHub pull requests and GitLab merge requests to the right ticket (or create it).
• Zazu writes the release note of each delivered ticket.
• Sébastien writes your weekly release note, and newsletters when you ask for one.
• Claude takes on the tickets that enter the Claude step of your workflow, and reports its result on the ticket (how to set it up).

Agents are sorted by theme: Customer feedback, Tickets, Roadmap and Announcements. A sentence at the top counts how many act on their own, and each row shows its mode (Acts on its own, Suggests, you approve, Paused or In a ticket) next to its switch. Click Customize on a row to see when it acts, what it changes and how to stop it, then its settings.

What can an agent change on its own, and how do I stop it?

Le Génie and Jiminy never change anything without you: they suggest a draft that you accept or clear. Five agents can act on their own, each within a narrow scope shown under Customize, in the Changes row:

• Baymax analyses each customer feedback you import into this product. Turn off the switch on its row to stop it: new feedback is then imported without analysis.
• White Rabbit moves the end date of overdue tickets every night. Turn off the switch on its row to stop it.
• Tic & Tac in Autopilot mode link or create tickets from pull requests. In Suggestion mode, they only suggest.
• Zazu fills in a ticket's release note when it reaches the publication step. Turn off the switch on its row to stop it.
• Sébastien writes a release note for each product view every week. Turn off the switch on its row to stop it.

No agent deletes your tickets or your customer feedback. Everything they do is signed with their name: under Customize, Last action shows the newest one, and See its activity opens the Inbox filtered on that agent.

What is the Inbox in the sidebar?

The Inbox collects what your agents produce and what needs your attention: pull requests to link to a ticket (accept or dismiss the suggestion), changelogs, release notes, rescheduled tickets… The number next to it counts what’s waiting. Above the list, two filters narrow it to one product or to some agents (tick as many as you like); See its activity under an agent’s Customize in Settings → Agents opens it already filtered. Open a message to read it: the agent and the product on top, then what it did, the ticket it’s about (click to open it) and one button to the result. A pull request suggestion shows the proposal, the pull request with the agent’s confidence, and Lier au ticket or Créer le ticket — or Ignorer. Once handled, archive an item: you’ll find it in the Archived tab.

Is my data used to train AI models?

No. Your data is never used to train AI. It is hosted in Europe, processed in line with the GDPR, and the platform is tested every year by an independent security audit (pentest).

What is a workspace?

The workspace is your team’s shared home: it holds your members, products, tickets, objectives, roadmap, settings and subscription. Most companies use a single workspace; everyone in it sees the same data, according to their role.

How do I switch workspace, and put my workspaces in my own order?

Click the name of your workspace at the top of the side menu: Switch workspace lists every workspace you belong to, with your role in each and a tick on the current one; click another to go there. At the bottom, Create new workspace.

Belong to several? Drag a line by its grip to reorder them: your order is saved on your account and follows you on every device. It only changes your list, not your colleagues’.

How do I invite a colleague?

1. Open Settings → Members (owners and administrators only).
2. Click Invite a member: a line opens at the top of the table. Enter your colleague’s name and email, then click Send the invitation (or press Enter).
3. They receive an email: the link creates their account and brings them straight into your workspace.

New members join as Builder. The member list is a table, one line per member: click a name or an email to correct it, the role to pick another one (each role says what it allows, see who can do what), the type (internal, external, customer), the teams, the products and the pipelines. Column headers sort the list.

Products and pipelines decide who can be assigned a ticket. A contributor, who reads everything and changes no ticket, shows Whole workspace there: a contributor can’t be limited to some products.

At the top, counters show how many members, admins, builders and contributors you have, and how many people have no product (they can’t be assigned a ticket). Click a counter to only see them; the product tabs and the search (name, email or role, e.g. “admin”) narrow the list too. Tick several members to add or remove a product for all of them at once.

What are the roles, and who can do what?

There are four roles:

• Owner: everything, including the subscription. At first, it’s the person who created the workspace. There is always exactly one owner: the role can’t be removed, only handed over.
• Administrator: everything the owner can do — settings, members, integrations, import — except buying, changing or cancelling the plan and the payment method.
• Builder: the everyday role of product people. Creates, edits, prioritizes and plans tickets, moves them on boards, manages Customer Voice. No access to settings or billing.
• Contributor: follows the work. Sees the backlog, the planning and the roadmap, comments, uses Ask and creates their own saved views — without changing the tickets.

Your role is shown in the workspace menu at the top of the sidebar. To change someone’s role: Settings → Members, then the role pill on their line.

How do I hand the workspace over to someone else (transfer ownership)?

Only the owner can do it, for example before leaving the company:

1. Open Settings → Members.
2. On the line of the member who will take over, click the crown (Transfer ownership).
3. Confirm with Transfer.

The member becomes owner: from then on, they alone manage the plan, the payment method and the invoices. You become administrator, and keep everything else.

The new owner must be a member who has already joined the workspace: an invitation that hasn’t been accepted yet doesn’t count. The owner can’t be removed from the workspace, nor see their role changed: transfer ownership first.

Can I belong to several workspaces?

Yes. Click the workspace name at the top of the sidebar: the menu lists all your workspaces with your role in each. Pick one to switch, or choose Create new workspace. Each workspace has its own data, members and subscription.

How do I change my name, photo or password?

Click your avatar at the bottom of the sidebar, then My profile. You can edit your name, photo, password and language, see the workspaces you belong to, your notification preferences and the tickets you own. Log out from the same menu.

Forgot your password? On the login page, click Forgot password and follow the link sent by email.

How do I get a colleague’s attention on a ticket?

In a comment (or any text), type @ followed by their name: they receive an email with a direct link to the ticket. The whole discussion stays attached to the ticket, so the decision is never lost in a chat thread.

Which emails will I receive, and how do I choose?

You decide, in two places:

• My profile → Notifications: turn on or off, per workspace, the emails you get as owner of a ticket and as assignee.
• The bell on a ticket: subscribe to a ticket you care about and pick what triggers an email — deadline pushed back, ticket done, ticket overdue, or a warning a few days before the deadline.

Every email has an unsubscribe link. Mentions (@) always send an email.

During your trial you also receive a few tips from the founder: see Which emails will I receive during my trial?.

What are teams and tags for?

Two simple ways to sort your tickets, managed in Settings → Teams and Settings → Tags:

• Teams group the people who work together (e.g. "Mobile squad").
• Tags are colored labels you stick on tickets (e.g. "Quick win", "Legal").

Both become filters everywhere in the app. An administrator can restrict creation so that only existing teams or tags are used — handy to avoid "bug", "Bug" and "bugs" living side by side.

Which tools can I connect, and what does each one do?

Everything happens in Settings → Integrations (owners and administrators):

• Jira, Azure DevOps and Linear: two-way sync of your tickets, statuses and fields.
• GitHub and GitLab: connect tickets to the code — branches, pull requests (merge requests on GitLab), issues, commits.
• GitHub Projects and Notion: import your boards or databases and keep statuses in sync.
• Google Sheets: turn the rows of a spreadsheet into tickets.
• Slack and Microsoft Teams: post your news into a channel.

Your AI assistants (Claude, ChatGPT, Cursor…) connect elsewhere: in Settings → MCP, under Agents (see MCP).

To bring tickets in once, use Import tickets in the sidebar: a page lists the sources — Jira, Azure DevOps, Linear, Notion, ProductBoard, GitHub Projects, Google Sheets or a CSV file — and the one you pick continues in a window.

From Import tickets, Import and sync (or Connect …) takes you straight to Settings → Integrations with that tool’s connection window already open: fill it in and the sync starts from there.

Each connection window has a grey column on the left that tells you where to find what it asks for — the token, the webhook address — step by step, next to the field.

Available integrations depend on your plan.

How do I import my tickets from a CSV file (Excel, Trello, Airtable…)?

Click Import tickets in the sidebar: the Import page lists the sources. Choose CSV File, and follow the guided steps in the window that opens — its grey column on the left shows where you are, what the step is for, and the template to download:

1. Upload: drop your .csv file (first row = column names). No file yet? Download the template: three example rows to replace with yours.
2. Mapping: say what each column is — title (the only required one), description, dates, priority, health, tags, teams, parent ticket… — and pick the target product.
3. Match types: match each value of your "type" column to a RoadmapHero type (you can create new ones on the way), or pick one type for all rows.
4. Preview: check the result — including the parent/child tree — before anything is created. Untick the rows to skip.
5. Importing: a progress bar, then a summary of what was created.

Almost every tool exports to CSV: Excel, Google Sheets, Trello, Airtable, Asana, Monday… That’s the easiest way in.

How does the Jira integration work?

What for: keep RoadmapHero and a Jira project aligned — product decisions taken here show up in your developers’ tool, and their progress comes back.

A wizard guides you:

1. Connect: your Jira domain (yourcompany.atlassian.net), your email and an API token (created in your Atlassian account, Security → API tokens).
2. Choose the Jira project to link to a RoadmapHero product.
3. Match the types (Story, Bug, Task… ↔ your types) and the statuses.
4. Optionally match fields (dates, tags, teams, and the sizing with your story points — see sizing), and import the existing tickets.

Changes then flow both ways. With auto-send, a ticket that reaches a status of your choice is created in Jira automatically.

How does the Azure DevOps integration work?

Like the Jira integration (see Jira), with the work items of Azure Boards. It works with Azure DevOps Services (dev.azure.com) and with your own Azure DevOps Server.

Setting it up: in Settings → Integrations, add Azure DevOps:

1. In Domain, enter your organization’s address (`https://dev.azure.com/your-organization`, or just its name) or your Azure DevOps Server collection’s address, and paste a personal access token (Azure DevOps: User settings → Personal access tokens) with the Work Items: Read, write & manage and Project and Team: Read scopes.
2. Project tab: choose the Azure DevOps project and the RoadmapHero product. The optional WIQL filter keeps only part of the project, for example `[System.AreaPath] UNDER 'Project\Team'`.
3. Types, Fields and Statuses tabs: match the work item types (Epic, Feature, User Story, Bug…), the dates, tags and sizing (Story Points, Effort, Size or a custom field), and the states, as for Jira.
4. Import & sync brings the existing work items in, parents first.

What it does: a ticket of a matched type is created in Azure DevOps, with its parent; its title, description, matched fields, status and dependencies follow. In the other direction, a work item created, changed or deleted in Azure DevOps updates RoadmapHero (a deleted work item archives its ticket, unless you untick it under Delete sync). The ticket shows its work item in the right column, with a link.

Automatic updates: RoadmapHero creates service hooks on the project. This needs the account to be allowed to manage them (the Edit subscriptions permission of project administrators): without it, a warning tells you so, and syncing from RoadmapHero still works.

Your token stays on RoadmapHero’s servers. To connect another organization later, paste a token of that organization too: the current token is never sent to a new address.

How does the Linear integration work?

1. Paste your Linear API key (starts with lin_api_, created in Linear under Settings → API).
2. Choose the Linear team to link to a RoadmapHero product.
3. Match the types: Linear has no ticket types, so you use your team labels — the special choice "(No label)" catches tickets without a label.
4. Match the statuses, then import the existing tickets if you wish.

Statuses and mapped fields then stay in sync both ways.

How does the GitHub integration work?

What for: connect each ticket to the code that builds it. Once connected, the ticket’s Build tab lets you:

• create or link a branch, open and merge the pull request, create and close issues, follow the commits;
• let Tic & Tac link new pull requests to the right ticket automatically;
• hand off the development to Claude Code: the app opens a draft pull request with a brief, Claude Code writes the code on the ticket’s branch, and you follow the progress on the ticket.

Setting it up: paste a GitHub access token, choose the repository and its default branch, adjust the branch naming pattern if needed, and link the repository to a product. You can also automate actions on your workflow — for example create the branch when a ticket enters development.

How does the GitLab integration work?

Like the GitHub integration (see GitHub), with merge requests instead of pull requests. It works with gitlab.com and with a self-managed GitLab.

Setting it up: in Settings → Integrations, add GitLab, keep `https://gitlab.com` in Your GitLab address (or enter your own GitLab’s address), and paste a personal access token with the api scope. Then choose the project and its default branch, adjust the branch naming pattern if needed, and link it to a product. To move to another GitLab address later, paste a token of that instance too: the current token is never sent to a new address.

What it does: in the ticket’s Build tab, create or link a branch, open and merge the merge request, create and close issues, follow the commits. The workflow automations and the options to create a ticket when a merge request opens and to fill the ticket description from the merge request work as on GitHub.

Automatic updates: RoadmapHero creates a webhook on the project so that commits and merge request status come in on their own. This needs the Maintainer role on the project: without it, a warning tells you so and the Re-sync from GitLab button of the Build tab still works.

Handing development off to Claude Code: on GitLab, Claude Code runs in your own GitLab CI. Open Set up Claude Code in GitLab CI (once per project) in the Build tab: add the `ANTHROPIC_API_KEY` (your Claude API key) and `GITLAB_ACCESS_TOKEN` variables to the project, allow pipeline variables for the Developer role, and paste the suggested job into `.gitlab-ci.yml`. Then Hand off to Claude Code opens a draft merge request with the brief and starts the pipeline; Claude Code pushes its commits and marks the merge request ready. The job uses your CI minutes and your Claude API key. If the pipeline cannot start, the tab says why and offers Relaunch Claude Code.

Tic & Tac also links new merge requests to the right ticket (or creates it), and Jiminy writes the ticket FAQ from the merge request description, as on GitHub. Only Jiminy’s spec drafts remain GitHub-only.

How do the GitHub Projects and Notion integrations work?

Both let your team keep its habits while you get the roadmap, prioritization and sharing on top:

• GitHub Projects: paste a GitHub token, choose the organization, repository and project board, match types and statuses, then import. Move a card in GitHub and the ticket follows here — and vice versa.
• Notion: create an internal integration in Notion (notion.so/profile/integrations) and copy its secret; on each database to import, click ··· → Connections and add it. Then choose the database, tell which properties hold the type, the status and the parent, match the values and import.

In both cases statuses sync both ways, and items archived on their side are archived here too.

How does the Google Sheets integration work?

1. In Google Sheets, share the spreadsheet as "Anyone with the link → Viewer".
2. Paste its URL in RoadmapHero, pick the tab and the header row.
3. Match the columns, the type values ("(Empty cell)" catches rows without a type) and, if you want, the status values.
4. Filter out the rows you don’t want, check, and import.

It’s an import: run it again when the sheet has new rows — rows already imported are recognized.

How do I send our news to Slack or Microsoft Teams?

Slack and Teams receive your news (deliveries, release notes); they don’t sync tickets.

• Slack: click Connect Slack in the integrations, approve in the window that opens, done.
• Microsoft Teams: in the target channel, choose ··· → Workflows → "Post to a channel when a webhook request is received", copy the address it gives you, and paste it in RoadmapHero with a label. You can add several channels.

Then choose what to post from the Share window of each shared room.

How do I connect my AI assistant (Claude, ChatGPT, Cursor) to RoadmapHero?

Through MCP (Model Context Protocol): you talk to your assistant as usual — “sum up this week’s customer feedback”, “create a ticket for this bug” — and it works directly in your workspace.

Everything is in Settings → MCP, right under Agents:

1. Turn on the MCP server.
2. Under What your assistants can do, choose the rights (see below).
3. Under Connect an assistant, pick the Remote server (recommended, nothing to install), copy its URL, then generate a workspace API key (owners and administrators). You can have up to 5 keys, each with a name: one per tool or person. A key is shown only once: copy it somewhere safe.
4. In Claude: Settings → Connectors → Add custom connector, then fill in the name, the URL and a header named x-api-key whose value is your key. In ChatGPT, add the URL as a connector with OAuth: a RoadmapHero page opens, paste your key there. Developers can also use the Local server (npx).

A key gives access to your whole workspace: never share it publicly. If one is lost or leaks, revoke it — the revocation is immediate and the other keys keep working — and create another one.

What can my AI assistant change through MCP, and can it delete tickets?

Settings → MCP → What your assistants can do says it in one sentence and three switches:

• Read your workspace: always on.
• Create and edit: off by default. Turned on, your assistant can:
• create and edit tickets: title, description (formatted as in the app), dates;
• move a ticket in its workflow: when it reaches a done step of the product’s delivery pipeline, its changelog is written, as from the board (and, as for an edit in the app, it is kept up to date when the agent changes the title or description);
• set the HeroScore: the importance of the ticket for each objective (Critical impact… Low impact), each business unit (Must have… Won’t have), each customer and each segment (Blocking… Minor), the Building and Maintenance efforts, the Uncertainty, and the text explaining the priority;
• work on objectives: create them, rename them, choose their products, create and update their key results, record ticket contributions;
• create stakeholders: business units, customers and segments, each with its shared page, as from the app;
• assign and organize: set the Owner of a ticket and who works on each step, move a ticket under another parent of the same product, put it in a sprint, create, start and complete sprints;
• plan capacities: estimates, monthly allocations and maximum capacities, with the same limits as the Capacities page;
• comment on a ticket: the comment appears in its Build tab, signed by the agent;
• sort customer feedback: create and edit Opportunities, link an insight to a ticket (its customer joins the ticket, as in the app) or to an opportunity, change the status of an insight;
• share: turn the Shareable link of a shared view on or off, draft a newsletter (nothing is sent), write and publish What’s new entries;
• work in bulk: the same change on up to 100 tickets (status, owner, sprint, parent, sizing, dates or shifting them by a few days), or up to 50 tickets created at once.
• Delete tickets: off by default. A ticket deleted this way is deleted as from the app (its children move up one level); products and blocks can never be deleted through MCP. The same switch lets your assistant delete a sprint that has not started and remove a What’s new entry.

Reading covers the whole app too: members, roadmap of a period, sprints, capacities, comments and the Activity of a ticket, Opportunities, shared views and What’s new.

Only owners and administrators change these switches. Create and edit applies to the remote server at once, including assistants already connected and every key: no need to revoke anything. The local server can always create and edit.

How do I know what an AI assistant changed in my workspace?

Open the ticket: its Activity log shows every change made through MCP, like the changes made by your team, credited to the name of the key that made it (for example “Claude Code updated the title”), followed by via MCP next to the date. Give each tool its own key, with a clear name, to tell them apart.

• A ticket created or deleted by an assistant appears there too (“… created the ticket via MCP”), as well as status changes and HeroScore inputs.
• An assistant connected through the local server (npx) shows as MCP agent.
• A ticket moved by a Claude step is credited to Claude, with Claude step.
• An action you confirm in Ask stays under your name, with via Ask.

Type the key’s name in the Activity search to see only its changes.

What do the colored dots next to my integrations mean?

• Green (pulsing): connected and active.
• Orange: connected, but the setup isn’t finished or the sync is paused — open it to complete the missing step (often a type or status mapping).
• Gray: not linked to a product yet.

What happens to my tickets if I disconnect an integration?

You choose: keep the tickets in RoadmapHero (they simply stop syncing) or remove the imported tickets (they are archived). To avoid accidents, you’re asked to type a confirmation phrase.

In all cases, nothing is ever deleted in the external tool: RoadmapHero only touches its own data.

What will I find in Settings?

Settings (at the bottom of the sidebar, owners and administrators) lists its sections in a column on the left, in four chapters:

• Strategy: Products (your products and their ticket types); Business goals, Business units, Customers (who and what you work for); Prioritization (how the HeroScore is weighted, see how).
• Organization: Workflows (the pipelines and steps of each ticket type), Teams, Tags, Custom fields and Custom wordings (adapt tickets and vocabulary to your company).
• Connections: Agents (your AI agents, see the agents), MCP (connect Claude, ChatGPT or Cursor to your workspace, see MCP) and Integrations (Jira, Azure DevOps, Linear, GitHub, GitLab, Notion, Slack…).
• Workspace: Members, Customization (your workspace’s logo, see how), Plan & billing (your plan and invoices, see billing), Export (download your tickets as CSV) and SSO (sign in with your company account).

The double arrow at the top of the column folds it to its icons, to give the section more room; your choice is remembered.

A section your plan doesn’t include stays visible and explains what it offers.

How do I add my company’s logo?

In Settings → Workspace → Customization, click Add a logo and pick a PNG, JPG, WebP or GIF file of 2 MB at most (a transparent background looks best). Replace the logo changes it, Remove takes it off.

The logo shows at the top of your What’s new page; Show the logo, in its Appearance, hides it from that page if you prefer.

Only the workspace owner and administrators can change the logo.

What is a product, and should I create several?

A product is a container for tickets that share the same types and workflows — typically one per app, service or major project. Create one product per thing you want to plan and communicate separately (e.g. "Mobile app" and "Web app"); every page can then be filtered by product.

Create and configure them in Settings → Products: a guided setup asks for the kind of project, the ticket types, the tools to connect and the people to invite. The number of products depends on your plan.

How do I add my own fields to tickets?

In Settings → Custom fields, create fields like "Country", "Estimated revenue" or "Legal review needed", and reorder or hide the built-in ones. It applies to every ticket of the workspace, and custom fields become filters too.

Each person can also rearrange the fields for themselves, with Configure fields on a ticket.

How do I export my data?

In Settings → Export:

1. Pick the product in the tabs at the top.
2. Under Which tickets, narrow them down if you like: a creation period and statuses (none ticked = every status).
3. Under Columns of the file, click the pills of the information to include (ticket fields, attributes, custom fields); Select all ticks them all.
4. The line at the foot of the card counts the tickets and the columns: click Download CSV.

The file opens in Excel or Google Sheets. You stay the owner of your data.

For visuals, the Planning and the Roadmap export as an image (see how).

Can we log in with our company account (SSO)?

Yes, on the Enterprise plan: in Settings → SSO, connect Microsoft Entra ID or Google Workspace. You can make SSO mandatory, keep password login as a fallback, and remove access automatically when someone leaves the company.

On every plan, anyone can already log in with their Google or Microsoft account from the login page.

How does the free trial work?

Every new workspace gets 7 days free, with all features. A card at the bottom of the sidebar shows the days left, with a Choose my plan button.

When the trial ends, the workspace pauses and the app asks you to choose a plan (the card then offers Reactivate my workspace). While it is paused, its pages, its MCP connection and its API keys are paused too; payment stays available to its owner. Your data is kept: pick a plan and you find everything as you left it.

What are the plans, and which one should I choose?

Four plans, from the lightest to the most complete:

• Starter: the essentials — backlog, priorities, Decisions, planning, roadmap, workflows, shared rooms, integrations, MCP for your AI agents (Claude, ChatGPT, Cursor…), Ask. Support within 36 h.
• Pro (the most chosen): adds Strategy — vision, objectives and OKR tracking. Support within 24 h.
• Business: adds Customer Voice and Capacities. Support within 12 h.
• Enterprise: adds SSO, a tailored onboarding and dedicated support, on quote.

Plans also differ by number of builders, products and daily AI messages. In the plan window, each plan shows its price excluding VAT, its products and builders (with what a builder seat comes to) and unlimited readers, no account needed. No commitment, by card or SEPA direct debit. For Enterprise, click Get a demo.

Click Choose: payment opens in the same window, with the price including VAT, your saved card if you have one (otherwise card or SEPA direct debit) and Change plan to go back to the plans.

Not sure? Use the trial to try everything, then ask us in the chat which plan fits your team.

Where do I change plan, update my card or download invoices?

In Settings → Plan & billing (in the Workspace chapter). The owner of the workspace finds there the current plan, seats and products used, the next renewal date, the billing address, the invoices, and Update payment info to change the card. Only the owner can buy, change or cancel the plan. The other members, administrators included, see which plan the workspace is on, and that the owner manages it.

Still on the free trial? The section says so and offers Choose my plan.

A plan change applies immediately, and billing is adjusted pro rata. Payments are handled securely by Stripe.

We agreed on a custom offer (yearly price, direct debit): how do I pay for it?

Once we have set it up for your workspace, the owner finds it in Settings → Plan & billing, in a Custom offer card: the plan, the agreed price excl. VAT per year (or per month) and how it is paid. Click Activate my offer: the payment window opens on that offer, with only the payment methods agreed (usually SEPA direct debit: you enter the IBAN of the account to debit).

The offer is active right away; a direct debit shows on your account within a few days, and the invoice is emailed to you and listed in Plan & billing. It then renews automatically at the same price, until you ask us to change or stop it. If a subscription is already running on the workspace, the window tells you to contact us so we switch it for you.

Why do I see a feature I can’t use?

Because your plan doesn’t include it yet. Instead of hiding it, the app shows what it would bring you, with a button to see the plans or to chat with us. The owner of the workspace can upgrade in Settings → Plan & billing: the feature is available right away.

If you’re an Administrator, a Builder or a Contributor, ask the owner of your workspace: the payment window tells you so if you click to upgrade.

Where is my data hosted, and is it secure?

Your data is hosted in Europe and processed in line with the GDPR. The platform goes through an annual penetration test by independent experts (the report is available on the Enterprise plan), and your data is never used to train AI. You can export it at any time.

Where can I read the terms of use, the privacy policy and the legal notice?

On three public pages, readable without an account:

• Terms of use
• Privacy policy
• Legal notice

Each page exists in French and in English: switch with the FR / EN buttons at the top of the page. The date of the last update is shown under the title, after Last updated:.

The links to the three pages are also at the bottom of the RoadmapHero presentation pages, under Légal.

I can’t see Settings, Import tickets or some pages. Why?

It depends on your role. Settings and Import tickets are reserved to owners and administrators, while the plan (Settings → Plan & billing) is managed by the owner only. Contributors see a lighter menu (Backlog, Planning, Roadmap, Inbox, Ask). Ask an administrator of your workspace to change your role if you need more (see roles).

I can’t edit a ticket or move a card. What’s wrong?

You probably have the Contributor role, made to follow the work without changing it. You can still comment and mention colleagues. To edit tickets, you need the Builder role or above: ask an administrator.

I didn’t receive my invitation email. What should I do?

1. Check your spam or promotions folder.
2. Check with your colleague that the email address is spelled correctly in Settings → Members.
3. Still nothing? Ask them to invite you again, or write to us in the chat.

My CSV import doesn’t look right. What should I check?

The usual suspects:

• The first row must contain the column names.
• In the Mapping step, each column must point to the right field (only the title is required).
• Dates must use the same format throughout the file.
• Broken accents? Save the file again as UTF-8.

The Preview step flags problems before anything is created: orange means a parent ticket wasn’t found (the row can still be imported at the top level), red means a hierarchy problem to fix first. You can also untick the problematic rows, import the rest and come back to them.

A shared link says "no longer available". Why?

The sharing was turned off by someone in the workspace (the Link switch of the room). Ask them to turn it back on — the same link works again — or to send you the new one.

The app looks strange or doesn’t show the latest changes. What can I do?

The app updates itself, but an old version can stay in your browser for a while. Reload the page (Ctrl + Shift + R on Windows, ⌘ + Shift + R on Mac). If the problem persists, try a private window, then write to us in the chat with a screenshot: it helps us a lot.

Is this help center up to date?

Yes: it is updated with every change to the product. When a page, a button or a rule changes in the app, the matching answers — in French and in English — and their illustrations are updated at the same time. The date of the last update is shown at the bottom of the page.

Illustrations are simplified drawings of the app: the real screen may differ slightly (your data, your wording, your plan).

An answer is missing or wrong. How do I tell you?

Write to us in the chat (button at the bottom of this page): tell us what you were looking for, or which answer seems wrong. We answer you directly, and add or fix the question here so the next person finds it.

How do I send an answer to a colleague?

Open the question, then click Copy link to this answer at the bottom of it. The link opens this page directly on that answer, in the reader’s language choice.