You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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:
This is usually the result of a Board Filter causing an error when its API is called.
One possible cause of this error is when the Board Filter specifies the Epic explicitly by its Issue Key, for example:
... "Epic link" in (AAA-999, BBB-888) ...
Are you able to check the Filter in the Board Settings? Editing the Filter Query to make sure it doesn't reference deleted issues may be able to resolve this problem.
If you would like to get into more specific details about your case such as sharing your JQL or configuration, feel free to reach out to me through our Support portal.
Stephanie Seymour | Easy Agile
My user is complaining, he cannot see the completed stories in the User Story Map.
is there a way to show the completed stories on the User Story Map Board?
he has a filter query, where he is just querying with keys and from 2 projects in the filter.
Hi @Afroz ARAB 👋
The story map will hide 'Done' stories in an active sprint or version by default, but that can be changed using the Filters menu, by including 'Done' as a status category. Please see: Why are 'Done' issues missing from my Story Map.
If that doesn't work for your user, could you please share the filter they are using via email@example.com and we'll take a look in more detail?
Tenille | Easy Agile