All ideas
Sort by:
Trending
Status:
Future consideration
Showing 6176
7
VOTE
Allow customization of report URLs
I create many different custom reports in Aha to communicate different things. The long URLs are difficult to remember and find though. I would much prefer to be able to create a report and save it such the URL is human-readable and meaningful. An...
3
Future consideration
4
VOTE
Ability to configure which users can be assigned to features/requirements
Currently every user I add to Aha is showing in the list of users that can be assigned to a feature/requirement. Even if the user is inactive, they still show in the list of users to choose from. I would like to have a check box on the user profil...
1
Future consideration
4
VOTE
Dependent Reports/Subreports
Currently if a report is being used in a large org by multiple teams, there's no clean way for each team to view a version of that report that is relevant to them. They can change the filters on the report but those then impact every other team, w...
0
Future consideration
6
VOTE
Option to Automatically add New Features and release to roadmaps
I am often times using that roadmap not only as way of visualizing the data but as the principal tool in which I can see all my projects and products at once, gain insight into the global picture of the work that is being done and then changing st...
0
Future consideration
2
VOTE
Use Epic Estimates option on Initiative
As a Product Owner who reports on the strategy initiatives, I would like for my "estimate" field on the epics to roll up to the Initiatives "estimate" field in a similar manner as Feature estimate's roll up to Epic's estimate field with the "Use f...
0
Future consideration
3
VOTE
Integration between Aha! and Jira Align (formerly Agilecraft)
Jira Align is a requirements tracking platform that was formerly Agilecraft, and is fully integrated with Jira. Our teams that are using both Jira and Jira Align are mapping their Epics in Jira to parent Epics in Jira Align, so that the roll-up pr...
1
Future consideration
1
VOTE
Improve handling of progress calculation for Develop team work
Features should have a single continuous flow that progresses from Design through Dev and QA, where statuses pick up where the last team left off. I.e., the final status of the record for the Dev team would be “Ready for QA” and map back to a simi...
0
Future consideration
1
VOTE
Enable Aha! community bulletin board for Aha! community
It will be helpful to reach out to (focused reach) all Aha! clients and inquire who solved the problems I am encountering. For example, instead of searching ideas and hoping Aha! solves a problem / blocker - others in the Aha! community may have a...
0
Future consideration
2
VOTE
Automation to Create Duplicate Record in Another Workspace
We have multiple teams who work in multiple workspaces where one body of work being created may trigger another body of work to be created. Currently we need to copy the record and then move the copy to the other workspace. Ideally we would be abl...
0
Future consideration
3
VOTE
