Application
Sort by:
Trending
Status:
Showing 7627
11
VOTE
Master Features and Features should be more interchangeable.
Aha wants to replicate the concept of epics as master features and features as stories. However, they treat them as separate entities which makes really hard to report a list of ‘features’ together (including master feature). For instance, JIRA ca...
0
Unlikely to implement
3
VOTE
Include outgoing dependencies in the "Other dependencies" timeline view
The "Other dependencies" section in roadmap views currently only includes incoming dependencies ('dependency of' relationship). We would like to see outgoing dependencies shown here as well ('depends on' relationship).
0
Future consideration
5
VOTE
6
VOTE
Ability to save a draft of an idea submission
Our portal is used internally to capture feature requests from the field. The form we use is failry complex in terms of the amount of information we require the Sales and Pre-Sales people to complete; often this can take time to complete. The requ...
2
Future consideration
4
VOTE
Add Initiative roadmap type that matches the feature default roadmap type
Would like to have the default Features/Epics Roadmap view option available for Initiatives. Instead of using release dates as the date an option to use Initiative end date would be ideal or make it configurable.
3
Future consideration
11
VOTE
Thumbnail Preview for Aha! links in Slack
It would be great if we could see the description of the idea when posting it through slack (or Workplace). Additionally, if we could vote through the thumbnail/preview, that would be awesome (not sure if this is possible though). Thanks!
5
Future consideration
7
VOTE
2
VOTE
Ability to Make Record Name Read Only
We want to make all Epic fields read only for Epics with 'Done' status, as it makes sense that done Epics should not be changed / edited anymore unless reopened. We applied a custom layout for 'Done' status in a workflow; however, it seems that 'N...
0
Future consideration
6
VOTE
Collapse audit history records on linked objects when a custom table is edited
When editing a custom table, linked records will have history records added which describe a new custom field being added. This creates noise in the history and makes the history of the object hard to track.
0
Future consideration
10
VOTE
Allow the maximum votes per person per idea to be higher
Currently there is a 10 vote per idea cap. It would be nice to be able to allow a user to use all their available votes on one idea. This would allow the user to show that out of all the ideas, a single idea is the most important feature for them....
2
Unlikely to implement
© 2024 Aha! Labs Inc.•All rights reserved