Team I am supporting is using New Feature > Story as their hierarchy to deliver on work. They are gross-estimating for purpose of PO prioritization at Feature level and then teams breakdown Features into Stories; and estimate on actual work.
**What is considered features in this case IS NOT really features - they used it "simply because".**
Since estimates are at both Feature & Story level, the story points are a summation however really the Feature shouldn't have any story points. I am concerned that the various Reports are representing incorrectly. I also find it difficult to visualize the parent>child relationships since Jira doesn't view it that way. Can use some sound boarding on this approach. What does everyone else do?
