Application
Sort by:
Trending
Status:
Showing 7689
2
VOTE
Visually represent the size of a feature with larger or smaller cards
In Aha, it's difficult to represent the relative effort required for different master features and features. Time is not the only consideration. For example, so features have dependencies that while not requiring heavy effort, will effect the dura...
1
Unlikely to implement
2
VOTE
Ability to count total number of objects within a product
It would be really useful to be able to list/count the total number of objects (requirements, features, master features, releases, initiatives, goals) across one or more products in a single pivot report.
This could be done by making a product in ...
0
Will not implement
1
VOTE
1
VOTE
Aha! Develop: Status mapping between Teams and Workspaces by shared workflow
When mapping statuses between a Team and a Workspace, I need to map each team one at a time. When teams are sharing the same workflow, I'd like to map each shared workflow to the current workspace statuses; rather than one at a time. This will all...
0
Future consideration
3
VOTE
Filter out unlicensed re/viewers from Workflow board configuration
The workflow screen functionality is only accessible to licensed users, so it seems distracting to display and have the opportunity to check them (or have to uncheck them), and even less useful to display them on the screen. I'm not sure that I wo...
1
Will not implement
3
VOTE
Ability to move and order linked features with a feature
Need the ability to move linked features around when there is more than one so that I can show priority.
We create a feature type called project - we have a large product portfolio - and within the project feature we link product features that rep...
0
Already exists
1
VOTE
Interactive AHA data model should not show objects NOT in use
AHA offers the ability to disable Epics. However, with Epics disabled across all workspaces, the interactive aha data model ("How AHA works") still shows this data object and a relationship of Feature to Epic and a link of "Work with Epics". This ...
0
Future consideration
2
VOTE
Glossary of terms/business context
Definitions for terms/concepts between product lines often vary. It would be great to be able to create a glossary/ubiquitous language archive where definitions can be linked to product lines or different products. This will help developers use bu...
2
Unlikely to implement
1
VOTE
Initiative to Release relationship tagging
When you are in an Inititive window, and select Add in the Releases section, you can add that various releases. If you look at the Release, it shows that it "Belongs to" the Initiative. But, there's no way to create the same releationship from the...
1
Already exists
2
VOTE
When creating a new Feature in Aha! and pushing the data to Jira: Aha! should have a way to handle sending data to Jira fields which are: a) required b) Autocomplete Renderer so the Epic can be created and not rejected by Jira
I created a new feature in Aha! When I attempted to send the changes from Aha! to Jira, expecting a new Epic to be created in Jira, I got the following error: The following required fields could not be set on the epic: Fix Version/s. Please check ...
8
Already exists
© 2025 Aha! Labs Inc.•All rights reserved