Dependencies

To reduce the amount of releases showing up on the GANTT chart of release overview, I would suggest adding the ability to filter on dependency links or not. Adding this filter capability give the user the ability to focus on release that inter-r...

When one of the feature is dependent on another feature, it will be great have a check on the status of each of the features so that the Dependent Feature should not be moved in "Commit" state before its corresponding dependencies are satisfied. R...

This is useful for us since on how we use AHA, its our technical guys who does the linking of dependencies in terms of other features/releases to another. There are internal processes in terms of approval before a certain dependency (record link) ...

The user will we able to import features/releases together with its record link dependencies. Especially with our way of using AHA, its very tedious for us to set record link dependencies one by one per feature/release. It would help us be more ef...

I love the visual dependency map. One enhancement I would like to see considered is that initiatives that have other initiatives roll up into them should show automatically in the dependency map even though an explicit "link" has not been establis...

The new Roadmap "Starter" report is very cool way to visually build roadmaps against multiple products. However I would not call this a report, this is a missing functionality to the releases section. This feature needs the ability to visually dr...

We use AHA across multiple sub-businesses. Our sub-business relies on capabilities delivered by another sub-business. It'd be much more efficient to make sure dependencies are properly mapped if I could make multiple features depend on another fea...

The dependency visualization is very useful. I'd like to be able to customize the contents of the tiles like in the Feature tiles. At a minimum, adding the Product Name is critical since you will only see Release Names in the current form and ther...

Adding the possibility to visualize also the requirements linked to each feature would give a much more complete picture of the feature backlog.

Right now, I have a task which depends on several other tasks, and some ofthose depend on the same underlying tasks. An example of this would looklike: A / | \B | C \ | / D I would expect the dependency map view to draw a line between B&D as ...