All ideas
Sort by:
Trending
Filter by:
Status
Showing 7148 of 7148
3
VOTE
Enable reporting on advanced estimates by individual team members
Currently, only the default capacity report supports visualizing estimates allocated to individuals within a team. In other report types, there is no reportable attribute for "Individual team member name" or similar. If users need to visualize the...
0
Future consideration
5
VOTE
Product Modelling based on Capabilities
Besides the ideas, features and epics management with aha, i would propose to add a functionality to "modell your product" - with that i mean a graphical modeller to structure the main functional and technical building blocks of my product. This i...
1
Future consideration
43
VOTE
8
VOTE
Add label dropdown select list when creating parent lines
Currently the only way to visualize multiple levels of goal or initiative rollups is to use the hierarchy report. Creating a hierarchy report can often be challenging because the labels used when creating parent lines are rarely defined to use con...
0
Future consideration
3
VOTE
Create Separate User Permissions for report sharing
Based on previous experience with other systems, I'd like to suggest a feature to restrict report sharing to certain user types. While any user can create and save their own reports for personal use, there is a concern that folks will save a large...
0
Future consideration
1
VOTE
Visual cue to identify if changes are automatically saved or not
While building out our environment, I have lost work because I didn't realize I had to save. On the Add a Scorecard, there is a visual at the top letting me know it is automatically saved. It would be great have this indicator on all setup screens...
0
Future consideration
2
VOTE
11
VOTE
Apply workspace templates to lines
Often settings like layouts, terminology, and navigation for parent lines may be purposefully different than workspaces. It would be helpful to drive standards for lines by allowing templates to be applied at those hierarchy levels. A few examples...
0
Future consideration
7
VOTE
Fix field population in Aha/Jira integrations to only rely on email address or other specific data
Today when the Aha/Jira integration runs it looks up users in Jira based on email, then failing to find a match it checks first name, then last name. Jira returns results for these and Aha will select the first return. The problem is that if we ha...
1
6
VOTE
Allow collaboration in whiteboards and notes with non-Aha! users
Product teams frequently need to collaborate with other cross-functional teams. Whiteboards and notes are great tools to facilitate this collaboration. It would be great to be able to share a whiteboard or note with someone who does not have a pai...
2
Future consideration