Skip to Main Content

Share your product feedback

ADD A NEW IDEA

All ideas

Showing 9095 of 9095

Map VSTS/TFS picklist custom fields to Aha! choice list fields

VSTS/TFS picklist custom fields are treated as strings and cannot support option mappings. Mapping a picklist field to an Aha! choice list field should provide the option to click Configure and map the choices.
Tessa Adair almost 6 years ago in Azure DevOps Services and Server 9 Future consideration

Automation to set a default estimate for all features created

I'd like the ability to set a default estimate for all features created. I checked the automation rules and the estimate field is not an option to update via automation rules. Some of our teams are doing a no estimates style of capacity planning w...
Guest about 4 years ago in Features 2 Future consideration

View in Aha! the author of a comment created in Azure DevOps

In integrations with Azure DevOps, comments created in ADO show the integration name rather than the individual as the creator of the comment when looking at it in Aha!. This can cause confusion for Aha! users who can't easily understand the conte...
Guest over 3 years ago in Integrations 1 Future consideration

Be able to select other record types from the new Roll-Up type.

We love the new Roll-up feature that allows you to link several roll-up levels to each other. One issue we are running into is being able to link other record types to the roll-up records. For example, when I create a pivot report, set the primary...
Brett Wilmeth about 2 years ago in Reports 1 Future consideration

Ability to use formulas to pull information from linked records into worksheets

Who would benefit? product owners/managers, program managers, project managers What impact would it make? While dependency reports are very valuable, it would be helpful to be able to pull in depends on record fields into the record with the depen...
Guest 10 months ago in  0 Future consideration

Allow multiple persona types to coexist for Products, Product Lines, etc

We need to be able to define multiple personas for individual products or product lines - currently only one template can be used for these entities. In addition to the user personas already in the system, we also need to have Buyer and Enterprise...
Guest almost 5 years ago in Application 2 Future consideration

Allow full link strings in search for relation

Would ease the use of the search function if it allows to insert the link (if in clipboard anyhow as this is often the case). Cumbersom to retype the prefix-featureNr-storyNr string...
Kaspar Hitzelberger over 1 year ago in Search 0 Future consideration

Show Ideas Workspace based on Organization

Who would benefit? End users accessing Ideas Portal. Customers showing only relevant ideas to end users. What impact would it make? It makes the users accessing the Ideas portal with ease. How should it work? Problem: we have 20+ products and the ...
Raghuraman Rajendran about 1 year ago in Ideas portal 1 Future consideration

Feedback on the UML design feature

What is the challenge? The snap feature for Aha! UML diagram should be more robust. Need for more UML templates. Export in more formats. Ability to develop Product report. What is the impact? The lack of a snap feature for some elements impacts th...
Guest 3 months ago in Whiteboards 2 Future consideration

Customizable header and footer section in shared web page

What is the challenge? When a shared web page is generated an automatic header is generated. This header is not editable and most often not aligned with Aha customer brand + not allows for navigational elements, contact information etc. What is th...
Mats Hultgren 5 months ago in Notes 3 Future consideration