All ideas
Sort by:
Trending
Status:
Showing 8939
7
VOTE
Having flexibility around Release Dates being either inherited from Rollup release or manually populated
We rely on Rollup releases quite a bit, however, from team's Feature board perspective it's often helpful to track "product" releases info, especially dates and be able to expose those accordingly. At this point, since we're using Roll up releases...
2
Future consideration
4
VOTE
Add unique organization vote count to ideas in portal
As a product manager, I'm interested in how many unique organizations voted for ideas rather than how many individuals. I can view this internally in reports, but I want customers to see the organization count next to an idea as well. A group of 5...
1
Future consideration
16
VOTE
2
VOTE
Consider inherited values when copying workspace settings for workspace templates
Who would benefit? Any users creating a workspace template from an existing workspace. What impact would it make? Today if a workspace template is created from an existing workspace, Aha! does not look at inherited settings. For example, at the wo...
0
Future consideration
17
VOTE
9
VOTE
Guided setup for Capacity Planning for Teams
It would be great if Aha! provided a step-by-step wizard to setup the Capacity Planning for Teams feature, very similar to how the current integration setup wizard functions. As an admin, I am not quite sure the sequence that I need to set up the ...
0
Future consideration
5
VOTE
Add option to merge field data when merging organizations
When I merge two organizations, it merges the domains nicely, but the custom fields I have created get overwritten. One customer (organization) can have multiple products (workspaces) and may have multiple values captured in a single custom field....
0
Future consideration
13
VOTE
Support mapping tags to JIRA multicheckboxes
Problem Overview It is possible to bi-directionally map tags in Aha! with custom multicheckboxes in Jira. However, it is not possible to configure how the values should map on each side. This creates errors when the two fields attempt to sync. Pro...
0
Future consideration
2
VOTE
Displaying requirements within the Retrospective report
Who would benefit? Our dev management team What impact would it make? Would provide much better insights into why a release went off track. Currently the "Records Added" section lists Epics & Features added after dev started. In our case, it's...
0
Future consideration
3
VOTE
Ability to refresh data from the development tool for a single Aha record
Sometimes I'd just like to fix a record or two that have gotten out of sync. When I click on the Integrations menu for a particular feature, I have the option to resend all fields to my development tool (Aha -> ADO), or, to delete the link. IDE...
0
Future consideration