All ideas
Sort by:
Trending
Status:
Showing 9093
2
VOTE
Add comment in history of record when performing a bulk edit
What is the challenge? The bulk edit feature allows a user to update a large amount of data, and sometimes you need to give additional context regarding the change. What is the impact? Without this context, users may be confused why their record w...
0
Future consideration
2
VOTE
Allow automatic imports of child records when parent records exist in a different workspace
What is the challenge? Currently, for Jira integrations, when you have parent/child records in Jira that span multiple Jira projects connected to multiple Aha! workspaces, all child records created will need to be manually approved as an integrati...
0
Future consideration
7
VOTE
Allow external team members to Approve work via To-dos
What is the challenge? We need to get some sort of Approval or Sign-off from our customers (not Aha! users under our account) on the requirement or feature that we have created for them. What is the impact? We need our external customers to agree ...
0
Future consideration
28
VOTE
12
VOTE
Cumulative Charts for Running Totals
Who would benefit? Roadmaps Users What impact would it make? Lovable products are the sum total of all of the incremental value delivered through iterative delivery over time. The impact of this capability would allow PMs to demonstrate that compo...
0
Future consideration
12
VOTE
Allow custom due date options for to-do automation actions
Who would benefit? Users who are looking to automate the creation of to-dos, approvals or work requests What impact would it make? Allow more flexibility in to-do creation How should it work? Similar to how we can select the custom date option whe...
3
Future consideration
94
VOTE
Ability to sort Comments by date and/or list most current first
I use the Comments field as a place to store Weekly Project status comments / and actions.. When team members visit the Aha! project it would be beneficial to have the most recent comments listed first versus scrolling down the list of comments to...
27
Future consideration
39
VOTE
Inherit field values from Epics to Features
By default, have the Epic based data values copied over to the Feature data fields when the user creates a new feature from an epic card. This eliminates the need for re-entering and possibly inconsistent values for the same fields. If inherited f...
7
Future consideration
6
VOTE
Copy object name with URL link (rich text format)
What is the challenge? When referencing object in chat with team-mates, I have to copy the URL link and then modify to include object name (feature name, release name, etc.). What is the impact? If I don't do that, my team-mates must open the link...
5
Future consideration
14
VOTE
Allow a list report embedded in a dashboard to show more than 50 records
Currently list reports, regardless of length, truncate at 50 records when embedded into a dashboard. This makes it very difficult to use dashboards to manage large portfolios. There is also no message informing you of the truncation, so we did not...
0
Future consideration
© 2024 Aha! Labs Inc.•All rights reserved