Issues Missing from Story Map


Issues you believe should be appearing on the story map are not present.


There are numerous potential reasons for issues to be missing from the story map, we have outlined them, and their solutions below. If none of these match your circumstances please reach out to us via the Customer Support Portal.

Quick Filters and Status Category Filters

There are two types of toggleable filters on the story map: Quick filters and Status category filters.

  • Quick Filters are filters native to Jira that can be set and defined by users.
  • Status Category filters are based upon the workflow-status of issues. There are three status categories that can be displayed, or filtered, on the story map: To Do, In Progress and Done. For more information on how we handle Done issues please see this article.

These filters prevent issues that do not meet their conditions from being displayed on the story map.


These filters can be enabled or disabled from the heading bar above the story map. See the image below as a reference.

Status Category Not Mapped

Jira provides the ability to create unlimited Statuses. Each Status must be mapped to one of three Status Categories: 'To Do' (blue), 'In Progress' (yellow) or 'Done' (green). If a status is not mapped to one of these three categories we are unable to detect issues associated with it through the API.


Filtering on the Fix this by setting a Status Category for each status in Jira. Steps can be found in this article from Atlassian.

Board Filter Query / Kanban Board sub-filter Query

Each board has a specific board filter query, designed to help teams focus on the work that matters to them. Sometimes these filters include clauses or restrictions that prevent the story map from rendering correctly.

The most common issues are when they exclude:

  • Epics, or other issue types
  • Done issues
  • Unassigned or Assigned issues
  • Labels or Components


Remove the exclusion clause from the board filter query, instructions on how to do this can be found in this article from Atlassian.