ADD A NEW IDEA

Application

Showing 7560

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) ...
Bonnie Trei 10 months ago in Releases 1 Future consideration

Ability to Configure Epic View as Default for all workspace views (Board / Prioritization)

Who would benefit? Enterprises who maintain Epic only or use Epic as primary record type. What impact would it make? Reduce confusion. The teams are currently directed to feature view on the board and prioritization view by default. Per Aha concie...
Hank Liu 8 months ago in Epic 0 Future consideration

Multi-language support in KBs

What is the challenge? Non-English speaking users need to access content in a KB. Currently a separate KB must be generated in each applicable language. How would you solve it? Provide KB translation. What impact would it make? Allow non-English s...
Emily Yankush 7 months ago in Knowledge base / Notes 3 Future consideration

Direct action to 'send to prioritized backlog' from Roadmaps feature

What is the challenge? I manage features in monthly releases and parking lots in Roadmaps. We also use Develop for sprint planning. I often need to move a feature to the prioritized backlog in Develop when I am working from the Roadmaps features b...
Todd Meyer 4 months ago in Backlogs / Sprints 0 Likely to implement
110 VOTE

Aha user management (groups, "mail to" communications, etc)

I would like to manage a large group of users (mostly commenters and reviewers) with some additional user management tools including: 1 - user groups - the ability to create groups of users and then assign product permission, workflow board visibi...
Guest over 9 years ago in Application 13 Future consideration

Indicate required fields when editing a record

We need the ability to make standard and custom fields mandatory for existing records. When a record is being edited, the UI should flag empty required fields so that the user is prompted to update them. This will help us ensure that critical inf...
Nathaniel Collum over 5 years ago in Account settings 12 Future consideration

Remove account/company name from portal email sender address

What is the challenge? If a company configures their email account (Ex.Gmail) using the same company name that they use for their Aha! account subdomain, emails sent via an ideas portal may display a phishing warning. This may occur because the fr...
Chris Quigley 2 months ago in Ideas portal 1 Future consideration

Have tag hierarchies

What is the challenge? If I use a pre-defined tag list to encode information such as a stakeholder team, I have to select all of the teams above that one in the hierarchy manually to be able to report at various levels. What is the impact? If I ma...
Guest 2 months ago in Epic 3 Future consideration

Allow team members with Aha! Develop permissions to be able to add and update research notes on features from Aha! Roadmaps

What is the challenge? When features are assigned to a team in Aha! Develop, team members that don't have roadmap permissions can not add additional documentation to the research tab as it attempts to add the notes to the Roadmap level Knowledge B...
Mike Lowery 4 months ago in Development / Knowledge base 1 Future consideration

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...
Guest about 1 year ago in Reports 0 Future consideration