Who would benefit? Product Managers and Owners What impact would it make? Prioritizing based on more than just custom fields allows us to quickly prioritize the work, rather than manually going through and entering in the priority. How should it w...
Frank S
12 months ago
in Features
0
Future consideration
There is a lot of flexibility with the user permission settings. As an administrator it would be nice if I could impersonate a user to identify possible issues. This feature is found in other applications in the market.
Guest
about 10 years ago
in User management
4
Unlikely to implement
Report on when Paid Seat users used a Paid Seat feature
The Last Active time for a user just tells us when someone last logged-on ( I think). To ensure our limited pool of paid seats is being used to greatest effect it would be good to get a report (CSV?) of when they last used a feature which needed a...
Keith Mantell
over 4 years ago
in
1
Unlikely to implement
Additional usage analytics -- reporting, customizations, etc.
We have many, many workspaces and customizations throughout our Aha! account. Having access to additional analytics related to usage would allow us to keep our account 'clean' and remove anything that is no longer being used or interacted with. Fo...
Shannon Sauvé
almost 3 years ago
in Reports
1
Future consideration
Bulk Delete Phases to Release/ Change Phase Template of Releases
I would like to bulk delete the phases under releases. The current process of deleting phases is time consuming as we have to delete one phase at a time. It would be best to have bulk delete option for release. We have experienced a lot of difficu...
Guest
over 6 years ago
in Releases
2
Unlikely to implement
Allow the JIRA integration to support mapping to more than one JIRA issue type and in Aha provide the ability to select the JIRA issue type to sync with
We use Aha for both Feature Requests and Defects and need to be able to designate if the JIRA issue type is an Epic, Story or Bug when linking to JIRA.
Kevin Konishi
over 8 years ago
in Jira
11
Already exists
Leverage AI to solve complex Aha! worksheet/calculated column formulas
It would be very helpful if I could describe the calculated column (or worksheet column) that I want in plain english, and have suggested formulas that work with Aha! syntax presented. This would help drive solutions faster and not get caught up i...
Madeleine Black
over 1 year ago
in Reports
1
Future consideration
In our organization we often times create hierarchy reports that show the product release, product master feature, and product feature.
We typically want to apply the same filter to all three: specifying the same product name and release name.
...
Michael Faust
almost 6 years ago
in Reports
0
Future consideration
Who would benefit? PMs sharing idea or org info with anyone else in our company What impact would it make? Allow us to use internal language instead of requiring an Aha translation layer How should it work? My company doesn't think in terms of rev...
Brian Trombley
12 months ago
in Ideas
0
Future consideration
We have been trying to position competitors on the “Competitor Matrix View” at product level. However we were expecting to see the competitors we have loaded in at the root product level line to add to the matrix. When the “competitor matrix view”...
Guest
almost 8 years ago
in Strategy
2
Already exists