All ideas
Sort by:
Trending
Status:
Future consideration
Showing 6266
6
VOTE
Ability to filter added/removed records in retrospective report
Who would benefit? Product managers trying to control churn within a release What impact would it make? It would enable us to more readily use this OTB report in change management of a release How should it work? We'd be looking for better general...
0
Future consideration
4
VOTE
Allow custom colors for custom table many-to-many fields
What is the challenge? I've set up a many-to-many custom table field to take the place of a multi-select custom field. I can't change the color of the custom table entries, like I could with the multi-select tags. It makes it difficult to quickly ...
0
Future consideration
5
VOTE
Add ability to import custom fields for To-dos
Who would benefit? Anyone looking to custom field data associated with their to-dos. What impact would it make? Teams can now define custom fields for To-dos within Aha! -- We should allow for teams to include important context captured as custom ...
0
Future consideration
21
VOTE
4
VOTE
Bulk import from HTML or JSON into notes
What is the challenge? Moving from a different KB source into Aha! Knowledge requires manual copying, pasting, and reformatting. How would you solve it? An import tool that accepts HTML or JSON would speed up this process. What impact would it mak...
1
Future consideration
14
VOTE
Allow a list report embedded in a dashboard to show more than 50 records
Currently list reports, regardless of length, truncate at 50 records when embedded into a dashboard. This makes it very difficult to use dashboards to manage large portfolios. There is also no message informing you of the truncation, so we did not...
0
Future consideration
9
VOTE
Automation of feature to another release based on custom field
Who would benefit? Product Management Team What impact would it make? Ability to cut down on manual work, reducing mistakes and time spent on administrative work How should it work? Under automations, be able to set a rule as such: When a feature ...
2
Future consideration
79
VOTE
User Story Mapping for Features/Requirements
Admins should have the ability to chose which records are in the User Story Mapping. We structure Aha! so that User Stories are at the Requirement Level so it makes sense for us to view as Features/Requirements
We don't use Master Features &am...
14
Future consideration
8
VOTE
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) ...
0
Future consideration
69
VOTE
Advanced Permission for Report creators
When I create a Roadmap or a report, I am effectively the owner. I can change any aspect of that report. However, at times I may be building it for someone else to use and manage, and I want the ability to change the ownership of that report at a ...
12
Future consideration