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
almost 7 years ago
in Reports
3
Unlikely to implement
Add comment in history of record when performing a bulk edit
What is the challenge? The bulk edit feature allows a user to update a large amount of data, and sometimes you need to give additional context regarding the change. What is the impact? Without this context, users may be confused why their record w...
Chris Quigley
2 months ago
in Reports
0
Future consideration
What is the challenge? When referencing object in chat with team-mates, I have to copy the URL link and then modify to include object name (feature name, release name, etc.). What is the impact? If I don't do that, my team-mates must open the link...
Lukas Slavicek
7 months ago
in Application
5
Future consideration
Capacity for teams: Update time-based estimate as record timeframe changes
Setting people estimates and then visualizing a report by people per month is a key capability in estimating team capacity and the ability to execute on a roadmap. When capacity for a team is exceeded, there are usually two recourses: Assign the i...
Gianmarco Spiga
over 3 years ago
in Application
3
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
over 9 years ago
in Releases
12
Future consideration
Who would benefit? everyone What impact would it make? limits information leakage and information misuse to parts of the organization who don't need to see in progress epic development before it's put in an official release How should it work? wit...
paul raisanen
10 months ago
in Account settings
0
Future consideration
What is the challenge? When moving from a ZenDesk knowledge base to an Aha! knowledge base, currently each document must be uploaded to Aha! individually. What is the impact? This would improve the speed for migrating tools. Describe your idea Add...
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
over 7 years ago
in Ideas
9
Future consideration
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) ...
Bonnie Trei
about 1 year ago
in Releases
1
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
almost 6 years ago
in Epic
8
Future consideration