Features
Sort by:
Trending
Filter by:
Status
Showing 1197 of 9094
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
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
Security per Feature or per Release
To enable consultants and freelancers to also provide estimates and work using Aha!, please implement more fine-grained security features to add user and choose from a list of features they are allowed to see and contribute. This is critical to en...
3
Unlikely to implement
1
VOTE
touch screen scroll from feature card view
I am constantly trying to scroll down on the feature board using my touch screen. It hasn't worked yet :) The cards are big so you can see them all so I often want to scroll up and down. Can you enable scroll from within the page (touch screen or ...
0
Future consideration
1
VOTE
1
VOTE
Feature mapping to Iteration and Epic
Currently, we have mapped Release to Iteration (which is by default) and to Epic. Hence features list displays the List of epics and the iterations/Sprints created as well. But, currently we are able to map the features to epic only. We are unable...
0
Future consideration
2
VOTE
Improve "Move requirement to another feature" dialog to help quicker find the required feature
Currently, if I need to move a requirement from one feature to another, I need to remember my destination feature name, and even then there could be several with the same names. Would be good to see and be able to search by more context, for examp...
0
Will not implement
2
VOTE
Seat assignment permission should be separated from billing
Assigning and un-assigning seats is weekly task as we have product and dev members joining and leaving.
Upgrade subscription is quarterly or longer term task as it depends on budget. In my opinion the first task should not require billing permissi...
0
Already exists
2
VOTE
Behavior of bulk edit product permission "to none" is not consistent with "from none"
When bulk edit product permission to viewer or product owner for example, product line permission of "none user" will change to the new value accordingly while other users will keep their their individually assigned permissions. This is ...
0
Unlikely to implement
1
VOTE
© 2024 Aha! Labs Inc.•All rights reserved