Application
Sort by:
Trending
Status:
Showing 7791
95
VOTE
Support release templates for rollup releases
When using master releases, it is not possible to select the release template for the sub-releases to be created. Which means the workflow to date looks like this:
Create a master release
Resist the temptation to select the products in the produc...
12
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
3
VOTE
Issue Types - Add ability to move an issue type to another workspace
What is the challenge? Within JIRA sometimes tickets get logged against a product/jira project which is incorrect. In that system we can either Move the ticket to another Jira project, or Clone and move the cloned ticket to another jira project. I...
0
Future consideration
7
VOTE
Allow multiple assignees on Features and requirements
What is the challenge? Many teams have more than 1 person working on something. For example a couple of devs and a tester could be working on a complicated feature together. We currently can't do that. Additionally for performance reviews it's nic...
0
Future consideration
7
VOTE
Include Frameworks in Reports
What is the challenge? The data model for Frameworks isn't available in Aha! reports What is the impact? We can't report on what's out there Describe your idea Add the data components for Frameworks to the custom report query builder.I guess it's ...
4
Future consideration
4
VOTE
Support integration actions within workspace template automations
What is the challenge? Currently, integration actions from automation rules can only be created for workspace-level automations. These automations can only be copied but cannot be applied to a workspace template. Currently, workspace templates are...
0
Future consideration
40
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
70
VOTE
Connected Tableau with Aha! for external reporting
As Aha! reporting features are not advanced / flexible enough to meet all our data analysis requirements, it'll help if it is possible to connect Tableau with Aha! directly so that we could handle the analysis by ourselves.
More importantly, Tabl...
3
Unlikely to implement
12
VOTE
Allow Release Date (internal) and Release End date (date range) to sync
Who would benefit? The Release date (internal) drives many of the OOTB reporting functionality in Aha! so it must be maintained and accurate for reporting to be accurate. For many teams, the end date of the release and the Release date (internal) ...
1
Future consideration
8
VOTE
Extend dependencies on custom roadmaps
What is the challenge? The existing functionality for showing dependencies in custom roadmaps only works for "depends" but not other relationships What is the impact? If we want to visualise dependencies on custom roadmaps, we can only select eith...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved