My votes
Sort by:
Trending
Filter by:
Status
Showing 8993 of 8993
28
VOTE
Group Custom Fields into sections
Very similar to APP-I-2199 I want to be able to group custom fields into distinct groups. For example I have a section that is all dates controlled by our development team. I would like to take those fields and group them together into one section...
1
Already exists
3
VOTE
Hide 'sign up' link on login page for private portals
Who would benefit? Customers What impact would it make? Cut down on support questions How should it work? If the portal is configured as a private portal, currently the user still see's the "sign up" link on the login page. If they click this they...
2
Future consideration
4
VOTE
Make all standard fields available for automation
Automation Rules are incredibly powerful but are limited to a very small subset of standard fields per item (ideas, epics, features, initiatives, etc.). We're constantly finding ourselves wish that a standard field would exist so that we can creat...
1
Future consideration
6
VOTE
Update workspace name/ID in record-reference-pill
As a product manager working with multiple workspaces, I would like the ability to change the workspace once a Feature has been created and have the new workspace name/ID update the displayed record-reference-pill copy/identifier automatically or ...
2
Future consideration
9
VOTE
Support logical operators in the "Feature name search" and similar filters
It would be helpful to be able to search for multiple terms on list reports, e.g. to return all features whose name contains "bug" OR "defect". Aha’s personal search uses logical operators but that is not the case for report filters currently.
0
Future consideration
31
VOTE
Adding Feature Workflows for Feature Types
Aha! allows you to create feature workflows for a product, but not for a feature type. It would be helpful to have product workflows applicable beyond the product - allowing users to customize completion workflows per feature type.
Let's look at ...
4
Future consideration
3
VOTE
Managing User Permissions at Workspace/Workspace Line Level
Workspace owners should be able to manage access at the workspace level. Currently, if a user has been given any access to a workspace line then that access is reflected in the workspaces beneath it. However, an owner of one of those workspaces sh...
1
Future consideration
5
VOTE
Populate Jira Components via Integration
Currently, as far as I am aware, the only way to use Components from Jira is to add a custom field in Aha! and map them. This works OK, however if a new component is added in Jira you have to manually add it to Aha! as an option to select. Please ...
0
Future consideration
14
VOTE
Add support for Jira Portfolio "Team" field
Jira Portfolio adds the Team custom field to JIRA. This team is used in Portfolio for planning. Aha! should support mapping this custom field so that the assignment of work and resource planning can be synchronized between Jira and Aha!
1
Future consideration
2
VOTE
Visually show when I add a text panel to a Dashboard
What is the challenge? When I add a text panel to a Dashboard, I'm not clear if my action has been successful. If the next available panel space in my Dashboard is not shown in my current screen, I won't know if it has been added or not. This coul...
0
Future consideration