All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5880
5
VOTE
'Copy feature' should copy pre-populated master field Custom tables too
When creating new features using Aha’s Copy Feature option, custom tables are unfortunately NOT showing the data pre-populated with the information filled in on those tables. Custom fields copy over with the data and so do custom tables of type Ma...
2
Future consideration
2
VOTE
Improve the order of search results / Favorites for all record types to simplify searching
When using the search function - sometimes you have to use such generic words that the result list of your search can be very long. A lot of these records that are found are not even touched regularly and you may not touch them for months or years...
0
Future consideration
2
VOTE
Epics as collections of Features (or Ideas) without being tied to a release.
We use Features as user stories that get individually worked within a release (development iteration). However, almost all of our Features roll up to Epics (which then roll up to Initiatives). The current format doesn't allow for the organization ...
0
Future consideration
2
VOTE
Ability to redefine date range by clicking and dragging (such as an epic or initiative) on a roadmap timeline view
This is a feature I previously had in ProductPlan, and I miss it horribly. Dates for releases, epics, initiatives are constantly in fluctuation, and currently there is no way to auto-adjust or even manually adjust the date ranges when a team gets ...
3
Future consideration
2
VOTE
Create Automations Across Separate Workspaces
Would be great to create automations to update a status of a record type in one Workspace based on an action taken on a separate record in a separate workspace. For instance, update my Initiative under a Product workspace when a record in a Market...
0
Future consideration
2
VOTE
Allow One to Many custom table relationship field to be more flexible
When creating records in a custom table that are linked to another record through the One to Many relationship field it forces the parent record to prepend to the name of the table record. If this record is then utilized elsewhere the name is elon...
0
Future consideration
2
VOTE
Share strategic position and personas exernally
I want to be able to be able to create a link to our aha! positioning and persona records so that they can be shared externally, and, when accessed, they include the most current information. Currently, we have to export as PDFs or PNGs and have t...
0
Future consideration
4
VOTE
Changing font style and size on feature card
Some items on the feature card you would like to stand out more. Fields like status or team name (custom field) are preferably shown bigger on the feature card. The feature ID typically shown in the top left corner could be shown in small fontsize...
0
Future consideration
2
VOTE
Approvals - Fixed Workflow
The Approval does not allow more than one person to approve – we wanted the reverse to have that one person can approve to move forward but we still want all people to have the option to approve for purposes of tracking. Once one of the two people...
0
Future consideration
1
VOTE
