Hi Jim,In my experience, you want to either use the Portfolio (Features etc.) with one 'layer' of User Stories under them OR use parent-child User Stories without using the Portfolio items at all. Mixing the two models can lead to messy data. It sounds like using Features as your Projects with the child User Stories under them would work well for you. You could tie the Features together under your next-level Portfolio Items (Initiatives?) if that helps. Using Portfolio Items gives you the ability to view roll-up data to report on progress etc.You would typically plan Features into Releases (these are not necessarily intended to represent Deployments but rather just a larger planning window, for example the Program Increment described in the Scaled Agile Framework). Features are estimated using the Preliminary Estimate (XS - XL drop-down with associated points values configured within your subscription) and Refined Estimate (numerical field that can be used to add a more specific number, either story points or some other number depending on how your organization looks at capacity). You can build a Release Capacity Plan based on your features, and then teams can build their more specific Sprint plans using just the points on individual stories. If you use the Capacity Planning page to build a feature plan and publish it, you can see current progress toward that plan on the Plan Progression page. The Release Tracking page also gives a great view of progress toward the features in the Release, with details showing which teams are working on which features in which sprints, what stories aren't scheduled yet, and any story-level dependencies within the Release.If you're using the portfolio at all, I can't think of any use cases for using parent-child stories.I hope that helps!