In making an easy story mapping solution for Jira we've had to make some assumptions about how a Jira instance is set up. For example;
There are two permissions that are required to create sprints and versions on the Story Map, Project Administrator and Manage Sprints:
Epic Issue Type Not Found
See Epics not displayed on story map
Status Category Filtering
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).
Categories help you identify where issues are in their lifecycle, particularly in places where a large number of issues are rolled up.
Old and Unused Epics Appearing on the Story Map
It is possible to mark epics as Done in Jira Software yet by default this does not move the epic into a Status of Done as Jira Software uses a custom field, 'Epic Status', instead.
If you have old and unused Epics, please mark them as done as part of the workflow. You can also automate the resolution of Epics by following these workflow steps to mak an Epic as done when it is resolved.
Atlassian has issues on their backlog for consolidation of this beahviour, see JSW-12500, JSW-9222 and JSW-8067.
Boards with Multiple Projects
Known Issues Specific to Jira Cloud
Jira Cloud APIs
We have encounteres shortcomings with the Jira Cloud APU. If you feel the pain of one or more of these, we would greatly appreicate you voting and commenting on the issue to show your support and encourage Atlassian to prioritise the feature:
On Jira Cloud, every add-on, including Easy Agile User Story Maps, has a system account to issues, search results, agile boards, fix versions and more. If this user does not have access to a filter or project the Story Map will fail to load.
To ensure the system user account (username: addon_com.kretar.jira.plugin.user-story-map) has access. confirm: