ADD A NEW IDEA

Application

Showing 7525

Ability to Hide Tab on Feature Cards

What: Hide Tabs on new look/feel experience for Feature Cards Why: Some information is more prevalent now in the view (e.g. Change Log) and may add confusion for our teams as we follow a different process for change management.
Guest about 4 years ago in Features 4 Future consideration

Workspace Type Field for Reporting and Ability to Convert Workspace Types

We are currently using only Product workspace types at my company. In updating our configurations, I noticed that our Product Owners have created IT and Project workspace types which is outside of the standard we have set. I attempted to create a ...
Cindy Datlof over 4 years ago in Account settings 0 Future consideration

Customization of User Story Map Detail page and "Comments" & "To-Do's"

We would like to be able to add custom fields on the detail page of User Story Maps. Also it would be helpful to have the usual "Comments" and "To-Do" section. This would be very helpful for our collaborative workflow.
Claudius Metze about 5 years ago in User story map 3 Future consideration

Integrate High Level Risk reporting

What is the challenge? Currently there is no automated way to visualize the tracked risks for reporting purposes (e.g. classical risk matrix) What is the impact? The user has to use multiple tools for reporting, instead of using Aha! as single sou...
Guest 3 months ago in Reports 0 Future consideration

Add option to expand Gantt view when sharing as webpage

When sharing the Gantt view as a webpage, the option to expand items (such as releases and epics) is unavailable to viewers. By allowing this functionality, the viewer could get a high level of understanding and expand items of interest to gain a ...
Guest about 1 year ago in Releases 1 Future consideration

Rename product value field in non-product workspaces

The product value score terminology works well for workspaces where teams are building products. But in other workspaces it can be confusing. In these cases a more generic field name would be easier to understand.
Austin Merritt over 2 years ago in Features 1 Future consideration

Enable milestone key dates in epic & enable to be used in custom roadmap

Our team uses releases by a timeframe, not by an individual product release. Thus our release is made up of multiple epics that need a milestone per epic. Please enable a milestone option at the epic level in both the epic & custom roadmaps to...
Steven Schafer about 1 year ago in Epic 0 Future consideration

Burn down by feature / epic / initiative

As a manager of business analysts I want to see the definition "burn down" of a given feature, epic, or initiative over time. For example, how much of a given epic or initiative is being defined vs. ready for development vs. ready for release etc....
Guest over 5 years 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

Need to roll up product initiatives to outside portfolio initiatives

Our Aha hierarchy is built out where are portfolios are fairly separate but still will have some dependent work. It would help us track those dependencies a lot clearer to have the rollup allow product initiatives to roll up to portfolio initiativ...
Wen-Wen Lin over 5 years ago in Strategy 1 Future consideration