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.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
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!
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.
Representing Story Map Activities as Jira Components
Edited
If you are looking to capture the 'Activity' level of the Story Map as explained in Jeff Patton's original blog on the practice, we recommend you use the Jira Component field.
Jeff originally shared this hierarchy:
In Jira, the nomenclature of the hierarchy differs. We like to think about it in these terms:
- Activity = Jira Component
- Task = Jira Epic
- Sub-tasks or task details = Jira Story/Task/Bug
Setting up Jira Components
To set up the Component level on a Story Map to represent an Activity you can use Quick Filters. You'll need a Project Administrator to create the Components first.
Here is the Quick Filter configuration for Jeff's Film Finder example:
Once configured, you'll see those Quick Filters across the top of the Story Map:
Create and Allocate Epics to Components
When creating an Epic, set a component:
Filter by Quick Filter
Finally, enable the 'Apply quick filters' option under the Views dropdown and then enable a Quick Filter:
