Features
Sort by:
Trending
Status:
Unlikely to implement
Showing 1196
2
VOTE
Configuring workflow board should be reflected for all users
Currently, if I was to configure the feature workflow board (and/or feature cards on workflow board), the changes I made would only be reflected back to me. Every user of the workflow board has to then configure the board (and/or feature cards) th...
2
Already exists
3
VOTE
1
VOTE
Display drafts when adding a new requirement without pressing save and leave screen as part of Requirements List
I was adding a requirement to a feature, and after inputting a considerable amount of details I needed to check another feature and lost the focus on the existing requirement. When I came back, I could not find the requirement and was quite worrie...
0
Future consideration
2
VOTE
1
VOTE
Easier way to create relationships between Features.
We have fund that creating relationships - Related To - between features is very value but I found myself not doing it because it feels cumbersome...and that's bad. I would live some sort of drag-n-drop a feature onto another feature and having th...
0
Future consideration
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
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
1
VOTE
© 2025 Aha! Labs Inc.•All rights reserved