What is the challenge? The new Aha! Roadmaps features board includes record-type options that some teams do not use. Administrators cannot find a navigation setting to hide these unused options. What is the impact? Showing unused record type...

What is the challenge? Closed or rejected features retain their rank in prioritization lists, leaving gaps in the ranking. What is the impact? Rank numbers keep increasing over time, requiring manual cleanup to maintain a useful list. Describe y...

What is the challenge? Users cannot define synonyms or article-specific search keywords to account for alternate wording, word forms, and spacing. What is the impact? Visitors can miss relevant articles when their search terms differ from the art...

What is the challenge? Search does not automatically prioritize phrases or query words appearing close together. For example, searching “dark mode” can rank an article that mentions “dark” in one section and “edit mode” in another above the ar...

What is the challenge? Title matches count double body matches, but users cannot adjust this weighting. Headings are treated as body text. What is the impact? Users cannot prioritize title and heading matches when those better identify the releva...

What is the challenge? Users cannot control how stop words are handled in queries or highlighting. What is the impact? Common words can produce broad results and distracting highlights. Describe your idea. Allow administrators to configure a s...

What is the challenge? The features board supports custom fields for grouping rows, but not columns. Teams that organize work using a custom field, cannot display those values as column headings instead of standard releases or workflow statuses. ...

What is the challenge? Today, we have an Aha Builder app that is integrated with our Aha account. We would like to have the app extract the content from a specified note in our Aha account and load it into the app. However, the integration today ...

What is the challenge? Capability field-status audit view Current Aha! reports return both of these conditions as the same blank/null result: 1. A field exists on a record but has not been populated. 2. The field is not configured or availabl...

What is the challenge? Some releases show 3 cards, some releases show 4 cards, instead of all cards. I would expect to see all cards in the release in this view, like we could before the feature board release. What is the impact? Seeing only 3-...