Thank you for you response. Any thoughts on how Feature requests relate to Epics (if at all)? We've been looking at Feature requests as something that either a customer or Product owner submits to drive Epics.
We like Epics to complete during a release. However, sometimes even an Epic is to big to get all of the desired functionality into a release. In this case, we are considering "Feature Request" to group epics that build the feature across releases. (And Epics group the user stories that build that feature).
It very much depends on how you want to manage your development work.
I tend to see features as stories with a different name (albeit a useful one which helps me see where they came from), and hence part of Epics, like stories are.
But yes, some feature requests might well be larger than Epics and need to be broken up into Epics and stories. At that level, I'd want to keep them separate from the stories, maybe with another project, or by using Portfolio and doing them as "initiatives" instead of features.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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