Application
Sort by:
Trending
Status:
Showing 7533
3
VOTE
Add Support for Workspace Rules in Automations
Who would benefit? All users What impact would it make? We currently have custom fields at the workspace level and would like to be able to create automations based on when those fields are changed. For example: We have a custom user field "Progra...
1
Future consideration
31
VOTE
Add "Use Case" management
Defining a vision, a set of goals and initiatives are important, but one thing that is missing is use cases. Some PMs don't define them because they can be a bit redundant or simply unnecessary, depending on the product and target market, but some...
8
Unlikely to implement
2
VOTE
Dashboard filters should not rely on underlying embedded filters
Who would benefit? Users with dashboards that have embedded reports. What impact would it make? It would make the dashboard filtering behavior far more intuitive How should it work? When you add a dashboard filter, the filter should be applied, ev...
0
Future consideration
3
VOTE
Add 'identity provider type' attribute to 'Update user' API endpoint
Who would benefit? Customers who manage user provisioning and updates through SSO and automated API processes What impact would it make? Customers can manage their user's authentication method en masse through the API - especially helpful with lar...
0
Future consideration
6
VOTE
Make Whiteboard Stickies Linkable/Clickable
I am beginning to use the Whiteboard feature to map out the Objectives and Epics my Product Team plans to work on each Program Increment over time. I want to be able to link the stickies on the Whiteboard to actual existing Objective or Epic recor...
5
Future consideration
28
VOTE
Group Custom Fields into sections
Very similar to APP-I-2199 I want to be able to group custom fields into distinct groups. For example I have a section that is all dates controlled by our development team. I would like to take those fields and group them together into one section...
1
Already exists
1
VOTE
Asking for more user-friendly IDs for custom table entries
What is the challenge? The current Custom table record IDs (e.g. 7576123412341234123) are long, complex, and difficult for users to remember and manage. What is the impact? Difficulty in communication and collaboration when users need to share or ...
0
Future consideration
31
VOTE
Adding Feature Workflows for Feature Types
Aha! allows you to create feature workflows for a product, but not for a feature type. It would be helpful to have product workflows applicable beyond the product - allowing users to customize completion workflows per feature type.
Let's look at ...
4
Future consideration
13
VOTE
Support One-to-Many relationship custom field on create screen
Part of our process for writing features is to essentially create a living document using the feature layout and custom fields. We created a Use Case(s) custom table that we turned into a one-to-many relationship custom field as each feature could...
3
Future consideration
3
VOTE
Update the salesforce integration to allow for two way communication on Proxy. I want the Proxy votes added in Aha to feedback to salesforce without building an API.
Who would benefit? This would benefit Aha, I am in a pilot phase with this functionality and if I cannot get around this piece (without asking for more development to build out API) I will have to go back to our previous process. This would also b...
0
Future consideration