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...
Ping Wang
over 6 years ago
in Reports
3
Unlikely to implement
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...
Guest
over 3 years ago
in Features
7
Future consideration
Currently workspaces can only be archived. They cannot be instantly deleted. This is a great safeguard to prevent real workspaces from actually being deleted. However it causes problems when you accidentally create a workspace as a line, or vice v...
Austin Merritt
6 months ago
in Account settings
0
Future consideration
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...
Guest
about 9 years ago
in Releases
12
Future consideration
Ability to view external links from Record Links reporting
What is the challenge? If you have External Link research concepts, and you bring in those Record Link relationships into a list report or Pivot Table, users cannot access the external link directly from the report. What is the impact? You will ha...
Stephanie Lechner
2 months ago
in Reports
0
Future consideration
We use the custom roadmap as our main overview. It will be really great if we have the option for dragging the features on this roadmap view as we can do on the starter roadmap.
Guest
about 6 years ago
in Roadmaps
13
Future consideration
Ability to send objects backwards/forwards in whiteboards instead of just to the front or to the back when layering multiple objects
Who would benefit? All Whiteboards users What impact would it make? This would enable users to easily order layered objects, which is particularly applicable when creating wireframes in the tool How should it work? Right now users can bring an obj...
Brittany Rhoney
8 months ago
in Whiteboards
1
Future consideration
What is the challenge? People often have an Epic or initiative reference number, but don't know the workspace name to request access. It would be helpful to have a prefix look-up tool with the Product look-up tool What is the impact? Users need th...
Mike Jacobson
5 months ago
in Account settings
0
Future consideration
Copying an epic should also copy the associated Features.
Currently, if I want to copy a Master Feature, I must copy the Master Feature, then copy each associated Feature and map them to the Master Feature. This is time consuming and doesn't make a lot of sense.
doug evans
over 5 years ago
in Epic
8
Future consideration
We have Improvement tickets in JIRA that we now (as new AHA users) want to migrate to ideas in JIRA. I have the JIRA integration created and would much prefer to import using the integration vs exporting tickets to CSV and then importing manually ...
Alex Horan
about 7 years ago
in Ideas
9
Future consideration