Application

Showing 7628

I want a user-impersonate option to let me and your staff debug user experiences

I want to login as a user with less rights (ie a simple contributor or reviewer) who has reported unusual behaviors I do not see myself. For example, I want to open incognito, go to an admin account feature, login as "impersonation" of a user I pi...

Kevin Martin over 1 year ago in Account settings 0 Future consideration

3 VOTE

Expand Milestones and Enable Milestone Reporting

Currently, Aha allows users to add milestones to features using the Gantt Chart view (example). These milestones can be useful for communicating intermediate value delivered to leaders outside of features, which may extend to 3 months or more in d...

Marcie Gardner over 2 years ago in Reports 1 Future consideration

11 VOTE

Convert a feature to an Initiative

we frequently see the need to uplevel a story with many requirements to an initiative level with many stories. Having this functionality would allow us to do this easily This usually happens when we start to groom a feature and realize it should b...

Guest over 9 years ago in Features 1 Already exists

8 VOTE

Simple report navigation

There needs to be improvements to the Reporting navigation. Informational viewers get lost in the Aha! UI for reporting. If you are a viewer, you should have a simple UI experience. For me, it should be directed UI experience.

Guest almost 7 years ago in Reports 2 Future consideration

9 VOTE

Lock release timeframe vs features

I'd love the ability to lock a release's start and finish date, and its children features have to stay within those dates. If they don't provide some kind of feedback or alert that the feature has strayed out of its bounds. Also, in the Releases...

Max Cascone over 7 years ago in Releases 0 Unlikely to implement

6 VOTE

Require approval for changes to certain fields

We would like to be able to 'lock down' some fields unless there is approval to change them. For example, Release date (or due date) Budget Designated people in the company would be required to approve any changes to these fields. Along with this,...

Kelly Sebes about 5 years ago in Releases 1 Future consideration

1 VOTE

Provide an ability to apply data formatting and justification settings for cells in pivot tables.

Who would benefit? All users What impact would it make? Numeric information can be configured to be displayed using right justification -- which is the norm. Currently, numeric data in pivot table cells are displayed with a left justification. Con...

Kelwin Y 10 months ago in Reports 0 Future consideration

9 VOTE

Allow Master Features to span multiple products

We need the ability to tie features from different products to a master feature

Guest over 7 years ago in Features 0 Already exists

2 VOTE

Allow exporting the schema of a scorecard through the API

When developing tools which use the Aha! REST API, it can be useful to check the schema that scorecards for a specific workspace/product use, in order to visualize this data. Currently, this can only be achieved by directly loading e.g. Ideas and ...

Guest over 1 year ago in API 0 Future consideration

4 VOTE

Change scorecards without erasing scores

Currently, selecting a new scorecard will erase all existing scores. The manual workaround is to export all your scores and re-import them again after changing the scorecard, but this is very tedious and non-obvious. Instead, allow the user to map...

Todd Meyer over 3 years ago in Features 0 Future consideration

Share your product feedback

Please enter your email address

FILTER BY CATEGORY