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
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.
We have Epics for larger features.
I want to replace Feature with Stories, but product team wants to keep Features as a high level request with use cases.
Wondering how your teams work with these 3 issue types and if one just gets cloned or promoted when needed.
I think if you ask 10 different companies, you'll probably get 10 different answers. :)
However, the generally accepted idea (supported by the Scaled Agile Framework SAFe) is a hierarchy where many stories form part of one feature and many features form part of one epic. Essentially it is a size description.
Have a discussion with the product team, try to understand why they want it like that and let them know why you want it changed, but in the end it doesn't make a huge difference
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.