A story map that stays linked to Jira.
CardBoard is a user story map that stays linked to Jira. Each card can link to one Jira issue, and the two share title, description, status, assignee, and story points, edited from either side. Where a card sits on the map never syncs, so you can recut a release on the map and your sprints in Jira stay put.
Jira holds the work. It doesn't hold the journey.
Jira is ordered by rank and grouped by sprint. That's the right shape for delivery and the wrong one for planning, where the question is what the user does first and what the thinnest release looks like. So teams map on a wall or a whiteboard, type the stories into Jira, and from then on only Jira gets updated. A month later the map is a photo.
The fix is to link the two and be strict about what crosses. What an issue is and where it stands should travel. Where it sits should stay on the map. Once the tracker can rearrange the map, the map turns into a second backlog.
Five fields both ways. Position never.
| Card field | Direction | Notes |
|---|---|---|
| Title | Both ways | |
| Description | Both ways | Jira rich text converts to Markdown and back. Unusual formatting can simplify. |
| Status | Both ways | CardBoard moves the issue through your workflow. If no transition leads there, the change is skipped and the card says why. |
| Assignee | Both ways | When the person has both a CardBoard and a Jira account. |
| Story points | Both ways | Whichever points field the issue type has. A size that isn't a number is skipped and the card says why. |
| Epic / parent | On import | Read when you bring issues onto the board. |
| Issue type | When created | Cards you send to Jira become the type you pick. |
| Acceptance criteria | Not synced | Jira has no standard field for it. |
| Position, release slice, color | Never | The map owns these. |
Statuses come from your own Jira workflow, so there's nothing to map by hand. Full detail, including disconnecting, is in the Jira integration docs.
How to do user story mapping in Jira, step by step.
Jira has no story map view of its own, so the map lives beside it and links in. Here is the whole loop, from an empty board to a release your engineers are working in Jira.
- 1
Lay out the backbone first
Start a story map board and write the steps a user takes, left to right, before you touch Jira. These are activities like "Find a product" or "Check out", not your epic names. If you start from the epics, you get your backlog again, sideways.
- 2
Connect the board to your Jira project
Open the tracker drawer, choose Jira, and sign in with Atlassian. You do that once, not per board. Pick the site and project. To leave Done work out, narrow it with a saved Jira filter.
- 3
Drag existing issues under the step they serve
The drawer lists the project's issues. Drag each one under the activity it helps with. Epic and parent links come along. An issue that fits under no step is worth a question: who is it for?
- 4
Fill the gaps and draw the first slice
Add cards for what the journey needs and Jira doesn't have yet. Then draw a line across the map for the first release, the thinnest set of stories a user would notice. Nothing in Jira changes while you argue about it.
- 5
Send the committed cards to Jira
When the slice is settled, send its new cards to Jira. Each one becomes an issue of the type you pick, linked to its card.
- 6
Deliver in Jira and watch the map
Engineers work the issues as usual. Status, assignee, and points changes come back within seconds, and a closed issue shows as Done on the map. For a team, have a Jira admin install the CardBoard app on the site so updates don't depend on one person's account.
Every write to Jira is made with the editing member's own Atlassian account, so your Jira audit trail shows real names. Guests can view, comment, and react without a Jira seat. Setup details, including the workspace app: Jira integration docs.
Who decides where a card goes?
Every Jira story-mapping tool answers that differently, and the answer decides whether the map still reads left to right as the user's path. Atlassian's own option is a User Story Map template on Confluence whiteboards, whose stickies convert to Jira work items.
| Tool | What places a card | What syncs |
|---|---|---|
| Jira-native story map apps (Easy Agile TeamRhythm and similar) | Jira. Epics form the backbone, order follows board rank, rows are sprints or versions. | It is Jira data, so everything matches. |
| Miro story map + Jira cards | You. Miro has a story map widget with releases. | Title, status, and more, two-way per card via webhook. Cards in the widget's task row can't become Jira issues. |
| StoriesOnBoard | Partly Jira. Hierarchy sync maps map levels to epics. | Title, description, estimate two-way. Status comes one way, from Jira. |
| CardBoard | You. Tracker changes never move a card. | Title, description, status, assignee, story points two-way. |
If your team won't leave Jira and wants the map to mirror the board exactly, a Jira-native app is the honest pick. If the map is where you argue about scope, keep placement human. The wider field is on our comparison of story mapping tools.
Where the Jira sync stops today.
- Acceptance criteria stay in CardBoard. Jira has no standard field to carry them.
- Parent links are read when issues come in. Re-parenting on the map doesn't change Jira.
- CardBoard isn't on the Atlassian Marketplace yet. You connect from inside CardBoard.
Frequently asked questions
- Can you do user story mapping in Jira?
- Not with Jira alone. Jira orders work by rank and groups it by sprint, and it has no view that puts the user's journey across the top. Teams add a Marketplace app that draws a map from Jira data, use Atlassian's User Story Map template on Confluence whiteboards, or map in a separate tool linked to Jira, like CardBoard.
- Does moving a card on the map change anything in Jira?
- No. Position, release slice, and card color never sync. Move a story into a later slice and the Jira issue keeps its rank and sprint.
- Can I start from an existing Jira backlog?
- Yes. Connect the board to the project, then drag issues from the tracker drawer onto the map. Epic and parent links are read on the way in. A saved Jira filter keeps the drawer to the issues you care about.
- Does every card have to be a Jira issue?
- No. Most cards in a mapping session are sketches. Link a card when the work is real. Unlinked cards stay on the map like any other card.
- Do story points and acceptance criteria sync?
- Story points sync both ways, through whichever points field the issue type uses. Acceptance criteria don't sync, because Jira has no standard field for them. If acceptance criteria matter to your process, Azure DevOps is CardBoard's deeper integration.
- Can people without a Jira account use the map?
- Yes. Guests are free on every plan and can comment on linked cards. Editing a linked card takes a workspace member signed in with their own Atlassian account, so Jira's history shows who made each change.
- What does it cost?
- Mapping is free. Connecting a board to Jira needs a paid plan, from $10 a month on Pro. Guests never cost anything.
On Azure DevOps? See story mapping with Azure DevOps. On Linear? See story mapping for Linear. New to the method? Start with the user story mapping guide.
Map it here. Ship it in Jira.
Build the map free. Connect Jira when you're ready to deliver, from $10 a month.