Search
Sort by:
Trending
Status:
Showing 62
1
VOTE
1
VOTE
Make search filters available when no results shown
Who would benefit? All users What impact would it make? Quality of life fix - there is a work around, but it's clunky How should it work? If I search for an idea and filter my results by workspace, then later go back to perform another search - if...
0
Future consideration
8
VOTE
Create Capability to Search and Sort "Internal Name" on Custom Field page
Aha Admin team is looking for a way to not hack the system by tracking custom fields used in AHA to Jira Integrations. Currently, the Admin team is adding a J* to the custom field name for each custom field with a Jira in the Name, API Key, Descri...
2
Future consideration
1
VOTE
Ability to search prioritized backlog from Backlog Management UI
Sometimes the prioritized backlog gets quite long, so from the backlog management screen, it would be helpful if the search applied to that as well instead of just the 'Product Work' and 'Engineering Work' sections. I use search functions almost e...
0
Future consideration
13
VOTE
Prioritize search results with exact matches
Using a real example: We have a single idea in our system with the word "Tagging" in its title. Entering the word "Tagging" into the search bar results in a large array of results where the partial match "tag" features somewhere in the item (e.g. ...
0
Future consideration
1
VOTE
2
VOTE
Combine tags with AND in filters
Combinations of simple tags are useful to categorise a feature (rather than single tags with complex meaning). It's more elegant and flexible. For example: 'settings', 'mobile' and 'web', rather than 'web settings', 'mobile settings', other kinds ...
0
Future consideration
1
VOTE
Make Integration fields from epic card searchable
We have a field on our epic cards called Integrations. It lists the ID# of the epid in ADO that our Epic in Aha is tied to. When I type a services id into my search field I do not find any results. If this were a searchable field in Aha I would ha...
0
Future consideration
4
VOTE
Component lookup by numeric id for relationships, hashtag referencing etc
Currently, when looking for a specific component via relationship or when using "#" in a note/comment etc and you know the id, you always have to put in the whole id including the workspace prefix. If you only use the numeric id, you don't see any...
0
Future consideration
1
VOTE
Ability to query data lineage to perform comparative analysis
PROBLEM STATEMENT: The current search history module is challenging in an of itself. It does not currently allow deep search, or specific query on objects leading to the user performing a generic search and sifting through endless pages. I'd like ...
0
Future consideration