Skip to Main Content

All ideas

Showing 961

Feature linked to multiple epics

Create ability for a feature to support multiple epics across workspaces. This will allow a single team that's working on a single feature that supports multiple epics across multiple teams. Currently we have multiple teams enabling a feature and ...
Steven Schafer 10 months ago in Features 5 Unlikely to implement

Link a Feature to multiple products

We regularly release features across Desktop, Web and Mobile which we have as separate products in aha. We would prefer to be able to have a feature which is linked across all products, as all are updated at the same time. We currently add feature...
John Hopkin over 8 years ago in Product 11 Unlikely to implement

Allow moving a feature to a completed release

Project Management is hard. I occasionally find tasks that were scheduled on a later release, but ended up getting completed, possibly due to a duplicate task, or the dev team pulled in a task from a future release. This is a pain since I have no ...
Chris Waters over 9 years ago in  8 Unlikely to implement

Decouple requirements from Features

Who would benefit? Users of AHA What impact would it make? Allow for my dynamics way of using AHA How should it work? One should be able to create a requirement (or whatever you want to name it) without being forced to link it to a feature. At Roc...
Guest 7 months ago in Features 0 Unlikely to implement

Add tags to Initiatives

Would like to be able to add Tags to Initiatives (in addition to the existing capability of adding tags to Features, Master Features etc.) We use tags to track Change Control and need to be able to do this at the Initiative level as well.
Julie Edwards over 5 years ago in Strategy 4 Unlikely to implement

View feature board for all sub-products at the product line level

We would like to see the feature board at the Product Line level for all products within the product line, including the ability to drag/drop prioritize and view details of each requirement.
Guest about 9 years ago in Features 7 Unlikely to implement

Integration with Microsoft Flow

You have Zapier integration which is basically the same, but we would rather use Microsoft flow... it cant be that hard once you have one to do another. Basically just requires you to apply and with your existing rest api's the rest will be fairly...
Guest over 7 years ago in Wanted 2 Unlikely to implement

Inherit Vision, Goals and initatives from other product lines

When initially setting up Aha it would be great to be able to have a Strategy for the Firm and then inherit and modify each of the elements by product line and product. This way you can cascade and align objectives easily. Vision, Goals, and initi...
Guest over 9 years ago in Strategy 5 Unlikely to implement

Add "Use Case" management

Defining a vision, a set of goals and initiatives are important, but one thing that is missing is use cases. Some PMs don't define them because they can be a bit redundant or simply unnecessary, depending on the product and target market, but some...
Guest about 9 years ago in Product 8 Unlikely to implement

Allow Requirement Dates to drive that roll up to a Feature to drive that Feature's start & due date.

We integrate with Jira Engineering work at the Requirement level and must see dates associated with Jira Stories as Requirements in Aha! Since addressing the Requirements / Jira User Stories make our Features a reality, we request that a setting b...
Guest almost 6 years ago in Account settings 4 Unlikely to implement