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
Recommended Learning For You
Level up your skills with Atlassian learning
Jira Align Program Essentials
Learn how to use Jira Align at the program level and how to plan for and manage your Program Increment (PI).
Managing Agile Boards and Reports
Learn how to pick the right board type for your team and customize it to fit your specific requirements.
Atlassian Certified Associate
Jira Software Board Configuration
Earn an associate-level credential from Atlassian that shows you can effectively configure Jira Software boards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.