Features
Sort by:
Trending
Status:
Future consideration
Showing 1185
1
VOTE
Enable Custom Object Terminology using more than one word
We would like to be able to customize the name of the "Features" object and menu item to "Features/Activities" to blend terminology between our Product and Project workspaces. The system does not recognize more than one word and will not pluralize...
0
Future consideration
1
VOTE
Ability to call attention to dates in notes/record descriptions
It is often necessary to call out important dates in a note or feature description. While it's possible to manually format the date, it would be nice if there was an automatic way to add a visual element to quickly call attention to these dates in...
0
Future consideration
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
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
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
Future consideration
1
VOTE
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
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
Future consideration
2
VOTE
