PINNED
Chrome extension to capture feedback from anywhere
What is the challenge? We work in many applications and Aha! can not build custom integrations for all of them. This makes it very hard to users of those applications to capture feedback and store it all in Aha! ideas. What is the impact? This res...
Allow for a cutoff timeframe to be specified for the Later column in Now, Next, Later
What is the challenge? PdMs have features planned for internal purposes out further than what we want the Now, Next, Later to show to internal business partners and customers. Because the later column is open ended "Future" it shows way more than ...
Guest
6 months ago
in Roadmaps
0
Future consideration
Removing the link between an Aha Feature and a Jira Epic should clear all fields included in the sync.
What is the challenge? When a Feature in Aha! is unlinked from its corresponding Epic in Jira, fields that were previously synced—such as the Aha! URL—remain populated in Jira. This creates a false impression that the records are still connected a...
Brittani Carmandi-Weber
6 months ago
in Integrations
0
Future consideration
What is the challenge? There are so many nuances to using Aha; the way items must be linked; certain fields are exposed when others are used. Aha is an increasingly complex software for us to use on a daily basis - and my colleagues and I find our...
Guest
6 months ago
in Application
0
Future consideration
Relating Features to Initiatives vs. Adding Features to Initiatives
What is the challenge? There are two ways a user can associate a feature to an initiative - but only one way officially links them. I am building various quarterly reports that display all features associated with an initiative. I went to each fea...
Guest
6 months ago
in Reports
0
Future consideration
Integration with Smartsheet - Indentation Mapping (Task Name)
What is the challenge? When establishing the integration Smartsheet with Aha!, the integration is very basic. It only allows us to map the information in Smartsheet to one type of item in Aha! (like Releases, Epics, Features ), and it only pulls i...
Albert Pivonka
6 months ago
in Integrations
0
Future consideration
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 2 years ago
in Capacity planning
4
Future consideration
Should be able to insert rows at any position in the custom table (like its on G - spreadsheet)
When i click to add row in a custom table the rows get added on the top. This could be desirable when you want to add comments so that the latest appears on the top but highly undesirable when you want to serialize items (1-n) with 1 appearing dow...
kanak l
over 5 years ago
in Custom tables
1
Future consideration
Support fractional teams when planning capacity by team
When using capacity planning for teams, it would be desirable to be able to indicate a resource is partially allocated to a particular team, e.g. 4.5 vs. rounding down to 4.0. There are many teams that have say ½ a resource allocated.
Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with
We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
Kevin Konishi
over 9 years ago
in Jira
11
Already exists
Don't show master feature name when stories from same master feature are next to each other
I was really excited to see this update: https://blog.aha.io/epics-and-features-planning/ However, I turned on the feature to show master features and immediately turned it off, and went back to my old way of just showing the epic name o...
Angela Wong
almost 7 years ago
in Features
7
Unlikely to implement