All ideas
Sort by:
Trending
Status:
Future consideration
Showing 5994
1
VOTE
Aha Configuration: use the custom terminology from the topmost Product Line
We use Aha's terminology option to remap several Aha terms to the words we use in our software lifecycle (thank you for that!). For instance, epics are re-labeled "initiatives", features are "epics", and requirements are "stories". However, the de...
0
Future consideration
1
VOTE
1
VOTE
Enable messages in dynamic forms to not always be a "dead end"
It would be quite helpful, if you could display a message to the user, and then still have the submit and back button. either though the conditions, or via a custom field, which can be populated from the backend, and added as a message during the ...
0
Future consideration
1
VOTE
Make the values from the Initiative Chart available to be added as fields to the Initiative Card/Details screen
Make the values from the Initiative Chart available to be added as fields to the Initiative Card/Details screen. The Effort/Value scores are visible in the Initiative Chart but not in the "Details" view.
0
Future consideration
1
VOTE
Email notifications alluding to the subject of the item not just the person
Right now, email notifications are presented in a "such-and-such created a to-do", this gives you no indication of what the to do is or why it is relevant, and thus makes it hard to separate the chaff from the wheat of Aha notifications
0
Future consideration
1
VOTE
Ability to remove stories that are in the integration from Aha!
Often times we only want a subset of what's in Aha! in our JIRA project. In some cases, when things get deprioritized, we want to remove them from JIRA but keep them in Aha! Would love the ability to do that FROM Aha! because keeping things in syn...
0
Future consideration
1
VOTE
1
VOTE
Provide a report to show required fields
As an admin, it would be helpful to have a report that would show all required fields by area - e.g. require fields for workspace, epic, feature, etc. and including workspace layout. This would help in the analysis of what fields are used and requ...
0
Future consideration
1
VOTE
Deletion of Product Lines should not restructure permissions
When a product line is deleted and it's children are preserved, they are moved to the top-level instead of being inherited by the parent product line. This creates issues with permissions and it should not be so difficult to restructure the worksp...
0
Future consideration
1
VOTE
