Working With the Map
A story map connects two views of the work: the user journey across the page and the delivery detail underneath it. In Story Maps for Jira, epics form the backbone and their related issues appear below them.
Read the map
- Backbone: the ordered epics that describe steps in the journey.
- Details: stories, tasks, and bugs that deliver a backbone step.
- Swimlanes: horizontal groups that show a sprint or release assignment.
- Unassigned lane: work that is not assigned to the selected sprint or release view.
Add and arrange work
Use Add to find an existing Jira issue or create a new one. Drag backbone items horizontally to clarify the journey. Drag a detail issue to change its order or associate it with another epic.
Keep different levels represented by distinct Jira issue types. The Basic edition uses the project’s epic type for the backbone. Advanced Story Maps supports configurable issue types and relationships.
Use filters for focus
Filters change what is visible; they do not delete issues or change the backbone. During a workshop, filter the map to the work relevant to the current decision, then clear the filter before checking the complete plan.
Keep Jira and the map aligned
Changes made through the map use the same Jira issues that appear in the backlog and boards. If a person cannot see or update an item, check their Jira project, issue, board, and field permissions. Avoid mapping the same work in several places unless the team understands which map guides the plan.
A practical team routine
- Agree on the user or outcome for the planning session.
- Check that the backbone tells a coherent left-to-right story.
- Add only enough detail to make the next scope decision.
- Order the important work before discussing dates.
- Move the selected slice into sprint or release swimlanes.
- Review unassigned work before ending the session.