Troubleshooting Easy Agile User Story Maps for Jira Edited



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; 

  • Kanban boards do not have an estimation statistics so the Story Map associated with a Kanban board does not show the estimation field
  • Agile boards containing multiple projects do not show the option to view by Fix Version as Fix Versions are specific to an individual project 


Known Issues


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.

  • Epics don't show (Jira Status Category is 'undefined')
  • Filtering on the Story Map is by Status Category
  • Fix this by setting a Status Category for each status in Jira


Status Category Filtering .png


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

  • Sidebar dissapears when switching to Story Map 
  • Unable to schedule by Versions 
  • We have not decided yet how to approach multiple versions which may be related yet are seperate (as versions are per project)


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: 


Filter/Project Access

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: 

  • the account has Browse Project Permission, for example use 'Application Role (Any logged in user)' for Browse Projects 


Project Permissions.png


  • the filter an agile board is based on is shared with Everyone, or shared using Project Permissions


Project Filters .png



Log in or Sign up to comment
Community showcase
Published Wednesday in Jira

Make your Atlassian Cloud products more secure: our NEW admin security guide

Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...

111 views 0 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you