ADD A NEW IDEA

All ideas

Showing 8928

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

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

When using a date range picker tab should advance from the start date to the end date

What is the challenge? Tab advances to next field, not end date What is the impact? I have to jump from keyboard entry to mouse. Other fields cycle on tab. Describe your idea when in first date, tab should jump to end date.
Guest 3 months ago in Features 0 Future consideration

An Epic Folder

What is the challenge? From a product planning and version management perspective, a product is divided into areas, each with a set of capabilities organized in categories. Each capability has features that evolve and are linked to an initiative a...
Guest 3 months ago in API 0 Future consideration

Draft with AI should use existing strategic records to produce better context

Who would benefit? Product and marketing teams author lots of strategic records in Aha! (vision, positioning, models, brand guidelines, notes + whiteboards, etc). All of this is important context to know when generating content with AI so the cont...
Max Robbins 7 months ago in Notes 0 Future consideration

Allow persona visual layouts to be locked so that they can't accidentally be adjusted

Who would benefit? Any user with permissions to move the visual persona layout around but who doesn't want to actually make any changes What impact would it make? Users would not be accidentally making changes and wondering how they did it, or try...
Melissa Hopkins 7 months ago in Strategy 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

A single Ideas Overview dashboard for an ideas portal integrated with multiple workspaces

Who would benefit? Aha users What impact would it make? It helps the business leadership team to look at the ideas statistics belong to different workspaces but a single product family under one umbrella How should it work? The same functionality ...
Ranjit Varghese 7 months ago in Ideas portal 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

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