I wish I could vote more than once for this. A combined view would be super valuable, especially if there was some way to expand the Master Feature to show the features under it in the Board and Workflow views. This should carry through to reporting where Master Features and Features should almost be treated the same in reports. e.g. it should be possible to generate a report where Master Features and Features appear inline together vs. being separated.
I will just mention that my team assessed Master Features as unusable with the current need to toggle back and forth
This is critical as we have both feature and platform teams that need to manage their work in Aha! on separate boards, but in so doing, we miss opportunities for efficiency, dependencies between teams, and gaps in requirements that having this feature would help solve.
Building on Wes's comments. The view should also allow us to show which products the master and child features belong to.
I would love this; would be awesome if we could have master features that can expand/collapse to reveal child features!
Same as the previous comment for me, an EPIC can have lots of little separate features within it, and to save having to move 20 individual features around based on its priority we could just move the parent epic and expand to see the child features within. At the moment I have to keep my child features in separate word documents so as not to clog up the board with tasks we haven't gotten around to yet.
Frankly having the ability to see two views would be useful:
- Release view with Master Feature -> Feature ribbon so you can expand and contract.
- Epic view: Similar to the Release board but instead of releases, Master Features. This would allow light story board organizing with parking lot features and epic/master feature organization.
I would love the ability to pull in master features into a release gantt for planning and not just features.
I'd have to echo everyone's thoughts, specially Jason's. We use Master Features as Epics and Features as User Stories and most of the epics are in the product backlog, while it is the user stories that get pulled into releases. Having them on two different views blocks our use case.
Second this, right now master features seem like an after thought to mirror jira epics only, but their full potential cannot be harnessed, in this one point assigning features to epics in jira by drag and drop is much more convenient
You won't be notified about changes to this idea.