In the knowledge base there are multiple articles with screenshots of Aha! that are used as visuals to help the user understand where in Aha! they should be navigating to when using a certain feature. However, I think many of these snapshots could...

We have multiple teams working on multiple Epics in JIRA that all track to a single Feature. It would be very helpful to enable integration of a Feature to multiple JIRA items.

I am a department manager who is focused on developing team capabilities and making improvements to people, processes, technology wrt my team. I'm looking for a way to create and track a roadmap of initiatives that can be implemented as part of ...

What is the challenge? Importing data from excel sheets as stickies What is the impact? Reduces the time to create stickies manually Describe your idea Allow the importation of data from excel to an Aha whiteboard, and create individual stickies f...

We update hourly rates on an annual basis. The Teams we define span Scenarios so we need to be able to define an hourly rate by Scenario for a Team. This functionality will enable flexibility in cost reporting and forecasting.

I'm trying to build a report that is exactly the same as what my users see when they search in the Ideas portal. I use this list to review with our design partners and early adopters. The Ideas portal search looks at custom fields while the filter...

Currently the ideas portal search function allows only the search of idea titles. Adding an advanced search function with options to search by originator or search within comments will make the system more navigable.

The Features roadmap currently contains the Feature Name and ID and you are not able to remove it. We have a use case where we have a custom field to capture the "marketing name" for our features that we would prefer to display on the Features Roa...

For longer Epic/Feature descriptions, I would like to have an automatic Table of Content that links to the headings, preferably where you can set the maximum heading level (e.g. only show heading 1s, only show heading 1 and 2)

How this would work: If an Aha ticket has "depends on" links Add the Pivotal Tracker ID for each Depended on ticket in AHA that has already been pushed to Pivotal Tracker blocker sections See PT API document here: https://www.pivotaltracker.com/he...