ADD A NEW IDEA

All ideas

Showing 5902

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

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

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

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

PI Planning event execution

Who would benefit? It would save a lot of time and reduce the manual effort of PI Planning preparation and event Execution. It will show that Aha is a tool for Portfolio management and also Planning. With extensive current effort of Aha to align t...
Milosz Konarczyk 10 months ago in Whiteboards 0 Future consideration

Improved Idea Notifications

Who would benefit? Product Managers/Owners What impact would it make? Improved communication How should it work? As customer feedback is entered as an idea, it is assigned to the associated Product Manager. There is no notification that a new idea...
Mike Levinson 7 months ago in Ideas 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

DevOps Integration: Sync "Task" Workitems with Aha's "To-Dos"

Currently, our main work in DevOps gets done within Task items which also have effort spent inside. These however are not a sync-option within the "To-Do" level of Aha!. The fields "Name, Description, Assigned to, Due Date (and maybe effort or oth...
Michael Scholze almost 4 years ago in Azure DevOps Services and Server 1 Future consideration