Skip to Main Content

Share your product feedback

ADD A NEW IDEA

All ideas

Showing 9110

Limit previous months visibility on Capacity Planning - Set Advanced Estimate Screen by time

I would like to limit the number of visible months in the Capacity Planning Detail view for any of my initiatives. See source issue: https://support.aha.io/hc/en-us/requests/499309
Mike Jacobson over 4 years ago in Capacity planning 0 Future consideration

Integration into Salesforce leads

We move customers from opportunity into lead generally before we can capture their ideas. They are then leads for their lifetime with our business. With the current Aha! Salesforce integration, we can't capture their ideas through Salesforce.
Melih Onvural almost 9 years ago in Salesforce 3 Future consideration

Improvements to Release Portfolio

The Release Portfolio is a good start on providing the ability to visually schedule resources, but it lacks some simple and extremely useful features: Simple leveling. There should be a way to assign resources to each feature, and level the sched...
Kristian Kauper almost 10 years ago in Releases 2 Already exists

Rank Initiatives

What is the challenge? Products often have more than 1 initiative to support goals. What is the impact? Teams don't receive clear consistent direction on prioritized initiatives Describe your idea Add the ability to Rank initiatives such that the ...
Penny Gerstner 7 months ago in Strategy 0 Already exists

Add option for adding use cases

What is the challenge? What is the impact? Describe your idea
Guest 7 months ago in Strategy 1 Will not implement

Allow team leads to manage workspace releases

Engineering managers & team leads sit "in between" Aha! Roadmaps and Aha! Develop. They more than just team owner permissions, but not full workspace contributor permissions. Key use cases Team leads can provide initial estimates on features b...
Jeff Tucker about 2 years ago in Account settings / Development / Releases 0 Future consideration

I want to rerank features in a release by master feature rank.

When pre-planning a release, I want to be able to move sets of features around under master features to ensure that there's enough capacity in a release to complete the full set of features under a master feature. To do this I want to rank all the...
Mat Jennings about 7 years ago in Features 3 Unlikely to implement

Component lookup by numeric id for relationships, hashtag referencing etc

Currently, when looking for a specific component via relationship or when using "#" in a note/comment etc and you know the id, you always have to put in the whole id including the workspace prefix. If you only use the numeric id, you don't see any...
Guest almost 3 years ago in Search 0 Future consideration

Make toggling between create/view layouts more obvious within the custom layout editor

The custom layout editor allows you to define the layouts for both the view screen and the create screen for a given record type. The admin needs to toggle between these 2 view types using a drop-down at the top of the screen. This drop-down was n...
Mark Eaves over 3 years ago in Account settings 0 Future consideration

Ability to select only one user from the "User Field" custom field

Currently the "User Field" (custom field) in Aha! allows you to select one or more Aha! users. It would be useful to have a "User Field" whereby a user can only select one user. This is important for us, as one of our User Fields sycnhronises wi...
Guest almost 5 years ago in Account settings / Jira 1 Future consideration