All ideas
Sort by:
Trending
Status:
Showing 9127
31
VOTE
Utilize Tags Across All Areas (Releases, Ideas, & Features)
Right now, you cannot use the existing default "Tag" field (used in ideas & features) within release layouts. If I want to add tags to a release layout, I have to create a custom tag field and cannot re-use any of the existing tags that were c...
5
Future consideration
9
VOTE
18
VOTE
Gitlab - Connect Master Features to Epics, and more
As one more request to improve connection between Aha and Gitlab :) We need better integration between Master Feature, Features and Requirements of Aha to Epics and Issues of Gitlab. A sample could be Master Features -> Epics and Features/Requi...
3
Future consideration
24
VOTE
Request for Workflow type board for Releases
We would like to see a kanban type board view for releases. The columns of the board would be used to represent status, and the cards themselves would be the release objects. This view is already available for Features, and we would like this styl...
5
Future consideration
26
VOTE
Enable more "filtering" possibilities in the Analytics Diagram
Dear Aha! Team,
my idea is about adding more filter possibilities in the Analytics Diagram Report.
Situation today
As of today the existing four filters on the Diagram report are not only used to filter, but also to hide/show a certain hiera...
3
Future consideration
3
VOTE
Feature Roadmap is appropriately scaled in Presentation
What is the challenge? Roadmaps do not present well in Presentation mode, (see attachment What is the impact? Maintaining a PowerPoint and Aha! version of the Product Roadmap risks lack of synchronisation and is time consuming Describe your idea A...
1
Future consideration
4
VOTE
Make it easy to prioritize a body of work's child records
Who would benefit? Teams who need to ensure clear prioritization on the subtasks within a body of work. What impact would it make? Right now, the only way to filter, for example, the features prioritization page to a specific body of work, is usin...
0
Future consideration
14
VOTE
1
VOTE
Per-document access control in knowledge bases
What is the challenge? Today, users can create separate knowledge bases for public consumption vs private consumption (via SSO or password), but they cannot create a single knowledge base that contains and manages access control of both types of i...
0
Future consideration
1
VOTE
Embed Jira views/tables into Knowledge Base
What is the challenge? Users sometimes want to be able to share live Jira views, such as issue trackers with their knowledge base users What is the impact? This will allow important information to be surfaced to users that is not typically stored ...
0
Future consideration
© 2025 Aha! Labs Inc.•All rights reserved