Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,556,526
Community Members
 
Community Events
184
Community Groups

'Issues are missing from the Story Map' - Easy Agile User Story Maps

Teagan
Teagan
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Jul 30, 2017

Each story map has a one to one mapping with an agile board. If you are missing issues on the story map it is good to check they are also present on the backlog of the agile board.

In this case, the missing issues may be excluded due to one of these reasons:

  1. the agile board filter excludes particular issues, e.g. project = FOO and component = BAR
  2. a status is not mapped to a column on the agile board 
  3. a status is not mapped to a Status Category*

 

* This is due to the required step of mapping Statuses to Status Categories not being performed after upgrading from a version of JIRA released prior to the introduction of Status Categories 

Comment
Watch
Like Be the first to like this
1103 views

0 comments

Comment

Log in or Sign up to comment
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

See all events