The competitor functionality right now represents the company rather than the products it markets, with products being represented as bullet points in the description. You therefore can't do things like e.g. have different pricing or strengths/wea...
Guest
over 8 years ago
in Strategy
1
Already exists
Many of our customers have tight email firewalls. Our IP addresses have been whitelisted for our transactional emails. It would be much easier if Aha let us use our IP addresses to send emails related to our ideas portal.
Guest
over 4 years ago
in Ideas portal
1
Unlikely to implement
A small annoyance. We use feature cards for stories and have long titles like "As a _, I need to do _, so I can _ ." The titles are hard to edit because the text field is a single line. The long line can't be seen all at once - I am forced to move...
Andrew Vit
over 4 years ago
in
0
Future consideration
Currently when deactivating a user, the user then becomes 'greyed' out. This isn't readily obvious due to coloring, resolution, etc.
Suggestion is to clearly annotate the user with a Joe Smith - Deactivated or something similar
Joe Carpenter
over 8 years ago
in User management
0
Unlikely to implement
Ability to create custom drop down with values from another custom field in another workspace
I would like to create a custom drop down field that appears on all Epics that use a shared layout. The custom field should be the available values in another custom field for a specific workspace. To illustrate: * On workspaces 1-10, I want to ad...
Guest
about 2 years ago
in Epic
0
Future consideration
I recently imported all our team's features from Jira into Aha! Develop. I later discovered that the prefix is not able to be changed. Currently, the only way to adjust the prefix would be to reimport them—either delete and then re-add from Jira o...
Allow all custom fields to be added to feature workflow board card layout
Today, the Feature workflow board will only show the custom fields for the "current workspace," but the workflow board can show records from multiple workspaces.
Customize fiscal calendar by year as well as month
We have a fiscal year which starts in March, but it's leading rather than lagging. Therefore, FY17 starts March 1, 2016. However, reports reflect March 1, 2016 as FY16