Skip to Main Content

Share your product feedback

ADD A NEW IDEA

All ideas

Showing 9041

Require completion of certain fields with promoted ideas

Epic, feature and initiative layouts allow you to require certain inputs when these records are created in the platform. But if they are promoted from an ideas, portal, individuals are able to bypass the completion of these 'required' fields.
Danielle A about 3 years ago in Ideas 4 Future consideration

Integration with Swift Kanban

The current Aha! Kanban board does not provide the flexibility other tools such as SwiftKanban provide. Is there any plan to build an integration into Swift Kanban and/or is there any plan to build out a more robust kanban board within Aha! We hav...
Guest over 5 years ago in Application 5 Unlikely to implement

Academy classes in different timezones

GOAL: Offer classes in timezones outside of North America | TIMEZONES: BST, AUS, IST.
Julie Price about 3 years ago in Training 2 Future consideration

Ability to sort Comments by date and/or list most current first

I use the Comments field as a place to store Weekly Project status comments / and actions.. When team members visit the Aha! project it would be beneficial to have the most recent comments listed first versus scrolling down the list of comments to...
Guest about 9 years ago in Comments / Notifications 26 Future consideration

Do not count description template as text when that field is required on idea submission

Who would benefit? Those utilizing the "template" option in description fields on ideas (and likely features) who have surfaced that field in portals and made it required. What impact would it make? Currently, if you have a template added for your...
Maria Plotkina 9 months ago in Ideas portal 0 Future consideration

Unique field layout based on feature type

As we continue to expand our use of Aha, one issue that has come up is that within a given product, there are different types of work/requirements that require different types of information. We're adding more and more custom fields, and it's star...
Zach Rose almost 8 years ago in Features 8 Future consideration

Expand/Collapse Release View to include Requirements

It's critical for our teams to see Features AND Requirements on the Release (Overview/Details View). You should be able to continue expanding down the hierarchy from Epic > Release > Feature > Requirement all within the Gantt.
Guest almost 6 years ago in Releases 7 Future consideration

Make viewing data in Aha! much easier and quicker, in less than 2 clicks

Users are really struggling with reports and roadmaps. They want to be able to find what they are looking for with just a couple of clicks and are overwhelmed with all the options presented to them under Roadmaps - as they have no idea what a pivo...
Deirdre Clarke over 1 year ago in Reports 2 Future consideration

Add 2-way integration mapping for release start and end dates

Release start date can currently only be mapped 1-way from Aha! to Jira (or any development system.) This is because that date used to be calculated based on features and phases in the release. Now that this date is set manually, it should be poss...
Austin Merritt over 4 years ago in Azure DevOps Services and Server  / Integrations / Jira / Rally 3 Planning to implement

Integration with WorkBoard

Our company is looking to adopt WorkBoard as our corporate standard for OKRs. Our development business units use Aha to manage our product strategy and roadmaps so we need to have integration between the 2 systems in order to maintain continuity o...
Joe Granville almost 4 years ago in Wanted 3 Future consideration