All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5843
2
VOTE
Add Table-Templates to support Build-Measure-Learn-Documentation
A thing thats missing in Aha! is the support of the Lean Startup Build-Measure-Learn-Feedback-Loop. The most lean way I could think of integrating this is to add a tables as templates, so you can build your own version of this https://digitaleneuo...
0
Future consideration
2
VOTE
Distribution list for empathy sessions
We have segmented client groups that consist of about 15 client representatives in each group. We have a process where we always review ideas with the members within that group. When scheduling an empathy session, it won't be applicable for us to ...
0
Future consideration
2
VOTE
Responsive Reports in Decks and Dashboards
When a report is put into a dashboard or deck, it should intelligently expand and contract to nicely fit the allotted space like any normal responsive web element. Right now, there is no way to make embedded reports look good for two people not on...
0
Future consideration
3
VOTE
4
VOTE
Assignee of feature in Aha! should propagate to Gitlab
As a user of Aha! / Gitlab integration, I would like to assign a feature in Aha to a specific user and have it show up as assigned to them in Gitlab, so that they are aware of the new feature and can take responsibility to break it down further in...
0
Future consideration
1
VOTE
Update Fredwin demo data with strategy data
The Fredwin demo sites have data in most of the areas. Please add demo data to the areas without demo data. Specifically we are looking at the strategy areas such as Personas, Models, and User story maps and the corresponding roadmaps related to s...
0
Future consideration
1
VOTE
Aggregate history / diff tooling for history
Sometimes information needs to be synced manually from Aha to another place or system. While this could be simple copy and paste, there are also cases where you cannot do that because the content is similar, not the same. E.g. when you use a diffe...
0
Future consideration
1
VOTE
Linked Record Statuses Change Based on Dependency
If I have a record linked to another in a separate workspace as a dependency, I would anticipate statuses to change when an action happens in the primary record. Example: Feature 2 is dependent upon Feature 1. If I move Feature one's status to In ...
0
Future consideration
2
VOTE
Custom Record Type, Made Up Entirely Of Custom Fields
We have some customer systems that we need to sync data back from. These are generally tasks that are created in systems we integrate with (specifically Azure Dev Ops, with the Task record). We are an outsourced product management company, so we h...
0
Future consideration
2
VOTE
