ADD A NEW IDEA

All ideas

Showing 8961

Support parent-child moving across workspaces and Jira projects

In the Aha! we have Features that reference a parent Epic in another workspace. In Jira we have issues that are children of an Epic in another project. This cross workspace/project relationship is supported in Aha! and Jira, but the integration do...
Michael Bruner about 3 years ago in Integrations 4 Likely to implement

Option to Remove Legend

Was thrilled with all of the presentation upgrades and then completely disheartened when I realized you still can't remove a legend. When doing reports for presentations often the coloring is more about getting the look of the report correct. The ...
Nicole Hardin about 5 years ago in Presentations 3 Future consideration

Allow filters at the panel level to panels included in dashboards

As a user I can define and add filters at the panel level to panels in a dashboard so that I can filter by different data points for different panels. For example I can add a status filter to a list panel so I can filter by project status (e.g. re...
Guest almost 2 years ago in Roadmaps 2 Future consideration

Add OKR enabled/disabled to workspace settings reporting

What is the challenge? With the introduction of the new OKR functionality in Aha! I can configure my individual workspaces/lines to enable OKRs but as an admin, I cannot quickly report on which workspaces and lines have enabled or disabled the OKR...
Justin Waldorf 7 months ago in Reports 0 Future consideration

Allow breakdown by Team for Detailed Estimates

The Initial Estimate Field of Epics and Features allows breaking down the effort values by Team. However, the Detailed Estimate Field does not allow effort to be broken down by team. You can only enter a value, but you cannot assign it to a specif...
Valentina Morales about 1 year ago in Capacity planning 4 Future consideration

Velocity-Based Planning

We'd like to estimate and plan releases based on velocity (rate of story point completion) rather than capacity (static value). This would enable more dynamic calculation of release capacity given a target release date and velocit(ies) over the d...
Guest almost 7 years ago in Capacity planning / Releases 2 Already exists

Show custom field names on integration errors

When there's an integration sync error with Jira on a custom field, Aha shows something like this: 'customfield_19011': Please fill out required fields The identifier 19011 has no meaning to us, as Aha doesn't expose a mapping of our custom field ...
Brian Trombley over 3 years ago in Jira 1 Future consideration

Allow multiple workflows in a product

Within a given product there can be different types of initiatives and features. Aha! supports the concept of feature types and allows templating of the description field by type. Would like to see an expansion of this concept to support configura...
Bonnie Trei about 5 years ago in Features 4 Future consideration

Default admin responses for each status

As a Product Manager, when I change an idea status, I want a default admin response to appear automatically. I could then tweak this pre-populated response as necessary and publish it. This would save me a lot of time during our idea triaging sess...
Elina Hu about 8 years ago in Ideas 2 Future consideration

Ability to move releases to other products

We create new products and releases for those products. Over time it may become apparent that the product, in fact, needs to be split up into additional products. Then, the releases must be moved. Each release contains phases and milestones with d...
Guest about 10 years ago in Releases 7 Future consideration