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
I am trying to find the best practice to use Jira hierarchy and implement it as part of the ALM process.
What hierarchy are you using today? Epic -> Story -> subtasks ? or something different?
i found out people are using different definitions for each issue type...
assuming you do follow the hierarchy i mentioned above, what your development board is presenting, Stories or subtasks?
i am trying to find the optimal solution for one jira project with multiple development teams, to cover also a case a feature can be handle by multiple teams...
WDYT , any thoughts
Thanks you for your input