Application
Sort by:
Trending
Status:
Showing 7681
5
VOTE
Roadmaps Improved Save Feature
Currently when we have multiple people updating the "Starter Roadmap" we find saving will overwrite previous changes if the previous save has not been explicitly loaded first. It would be nice to support "concurrent" editing and not losing changes...
0
Future consideration
36
VOTE
Ability to move releases to other products
We create new products and releases for those products. Over time it may become apparent that the product, in fact, needs to be split up into additional products. Then, the releases must be moved. Each release contains phases and milestones with d...
7
Future consideration
11
VOTE
Allow "Original Estimate and "Logged Effort" to be used in Calculated Columns
In Roadmaps list, having the ability to do calculated columns is incredibly powerful. However, we recently noticed that there are two fields we want to use to create charts that are not available to use. These are Original Estimate and Logged Effo...
1
Future consideration
5
VOTE
Update the Release associated with an Epic or Feature using Automation
We've integrated Aha! Roadmaps and Jira but the release information is not being synced. We can use automation to copy the Epic/Feature Release name to a custom PI field and use the integration to sync the custom PI field with Jira. But when the P...
0
Future consideration
15
VOTE
8
VOTE
Custom Field - Internal Name & Choice Lists Report Display
When creating reports with custom fields, there can be many fields within an account that have similar names that will display as field options. We use the internal name to help differentiate and allow the user to select the right field they are l...
0
Planning to implement
29
VOTE
Default admin responses for each status
As a Product Manager, when I change an idea status, I want a default admin response to appear automatically. I could then tweak this pre-populated response as necessary and publish it. This would save me a lot of time during our idea triaging sess...
2
Future consideration
5
VOTE
Scope / granular permissions for API Access
Hi All, currently every user with Aha! access can create an api token or authorize Apps to use the Api. And the Scope is tied to the user itself and not configurable. When it comes to projects, utilizing the API, it is the Application Owner / Admi...
0
Future consideration
4
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
25
VOTE
© 2024 Aha! Labs Inc.•All rights reserved