All ideas
Sort by:
Trending
Filter by:
Status
Showing 9035 of 9035
3
VOTE
Notification when admin response edited
What is the challenge? We are using the admin message as a change log to provide customers a history of what is going on behind the scenes with an idea until it becomes a feature. Updates to the admin message do not provide a notification to the v...
0
Future consideration
3
VOTE
Stop remembering my last search on the "Backlog management" page
What is the challenge? Every time I navigate to the Develop > Team > Backlog management page, the page is blank. It's blank because the page is remembering the last search I made. What is the impact? It's confusing. Takes me a minute to real...
0
Future consideration
3
VOTE
Insertion of documents into Whiteboards
What is the challenge? I use whiteboard for collaborative work. What is the impact? Having to come out of the Whiteboard to show a document breaks the thought process Describe your idea If we could add a document into a whiteboard that opens when ...
4
Future consideration
4
VOTE
Add the Option to Copy Over Links When Promoting an Idea
Who would benefit? All Equifax or Front Door Ideas feature users What impact would it make? Save time in linking dependency parents How should it work? 1) User links an un-promoted idea as a dependency of some Epic, Feature, Initiative or other wo...
0
Future consideration
45
VOTE
4
VOTE
New Custom Field Type - Calculated Field
Who would benefit? All Aha! Users What impact would it make? Significantly improve the reporting experience and provide users access to real time data at the record level. Users would be able to essentially add a calculated column by adding a data...
0
Future consideration
30
VOTE
On a public ideas portal: require a user account before posting, voting and commenting.
Our public ideas portal is today open for all people to post.
I’ve been recommended by our internal security expert to require people to create an account before allowing them to post, vote and comment.
When I set the ideas portal to be privat...
2
Unlikely to implement
26
VOTE
Keep features in sync when they cross areas in Azure DevOps
This is useful when you have your DevOps areas configured by team. Once the features are pushed from Aha! to DevOps and evaluated by the team they need to be moved into the area for the appropriate team. Any team can work on any feature based on a...
0
Future consideration
44
VOTE
Update Feature ID when moved to another product
When you create or copy a feature, its ID is automatically created based on the product code. The ID is a combination of the product code and an auto number (and that is perfectly fine). But when you change the release reference to a release of an...
10
Future consideration
8
VOTE
© 2024 Aha! Labs Inc.•All rights reserved