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
Hello Atlassian Community! Each month, we run a series of Spotlights to highlight Marketplace vendors and apps that our team thinks this Community would find valuable. In last month's S...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs