ADD A NEW IDEA

All ideas

Showing 5696

Support milestones in the release retrospective report

The release retro report currently uses only a single (pseudo) milestone: when development started. Some teams want to measure changes in the release relative to several milestones within a release, such as a beta launch, or code freeze.
Jeff Tucker about 1 year ago in Reports 0 Future consideration

Ability to Hide Tab on Feature Cards

What: Hide Tabs on new look/feel experience for Feature Cards Why: Some information is more prevalent now in the view (e.g. Change Log) and may add confusion for our teams as we follow a different process for change management.
Guest about 4 years ago in Features 4 Future consideration

Send report notification ONLY if there is data in the report

If a report returns no data then the notification shouldn't be sent via email. It should only send the notification if there is at least one row of data.
Steven Schafer over 1 year ago in Reports 0 Future consideration

Manage who receives email requesting document reviewer edit access

Who would benefit? Workspace owners who are currently receiving all requests to edit a document from a reviewer. What impact would it make? The request to edit a document will be reviewed and approved more quickly with less noise to owners that do...
Julie Price about 1 year ago in Notes / Whiteboards 0 Future consideration

Reduce real estate consumption in the header section

Who would benefit? All users of Aha What impact would it make? It would show more of what matters on the screen, increasing legibility and user productivity. It would also bring the relevant content higher up on the screen. How should it work? The...
Craig B 10 months ago in Roadmaps 0 Future consideration

Burn down by feature / epic / initiative

As a manager of business analysts I want to see the definition "burn down" of a given feature, epic, or initiative over time. For example, how much of a given epic or initiative is being defined vs. ready for development vs. ready for release etc....
Guest over 5 years ago in Reports 0 Future consideration

Need to roll up product initiatives to outside portfolio initiatives

Our Aha hierarchy is built out where are portfolios are fairly separate but still will have some dependent work. It would help us track those dependencies a lot clearer to have the rollup allow product initiatives to roll up to portfolio initiativ...
Wen-Wen Lin over 5 years ago in Strategy 1 Future consideration

Ability to enable/disable each email template for the ideas portal

We have ideas with hundreds of people voting and commenting on features and have received feedback from our users that they are overwhelmed with emails from the portal, in particular, the "User has Commented" email. We would like the ability to...
Guest over 7 years ago in Ideas portal 3 Future consideration

Return votes to users when an idea is marked as "already exists" or "will not implement"

Currently if you mark an idea as shipped it returns votes automatically to idea portal users because this is now in the system. I feel if a user puts an idea in and it is something that already exists and they just didn't realize it, when I mark i...
Guest over 6 years ago in Ideas 7 Future consideration

Provide a less disruptive warning when data is truncated in Reporting

What is the challenge? When I'm editing a report, I constantly see this warning. I'm aware that my dataset is quite large (and I'm actively trying to filter it down), but it's annoying to be constantly reminded via this popup. What is the impact? ...
Nathaniel Collum 3 months ago in  0 Future consideration