All ideas
Sort by:
Popular
Status:
Future consideration
Showing 6182
6
VOTE
Allow custom footer to KB pages
What is the challenge? Certain copyright, legal, etc. information must be included on each KB page. Right now, this text would need manually added to the bottom of each article. If it ever needed changed, each article would need edited. What is th...
1
Future consideration
6
VOTE
Embed a webpage within a Note in a KB
What is the challenge? When creating documentation to share in a Knowledge Base, sometimes you want to include information from another site. Currently you have to either : Copy and paste that content into the KB, so you have to maintain it in two...
1
Future consideration
6
VOTE
Template community to publish and find new templates
What is the challenge? I want to find template inspiration by seeing templates that other users of Aha! have made for their own purposes. The template library is a wonderful place to find high-quality templates, but I want to see what other templa...
0
Future consideration
6
VOTE
Edit phases with out using edit "pencil"
What is the challenge? We would like to be able to interrogate release phases without hovering over to find the edit pencil How would you solve it? Allow users to click on the phase name to edit or view phase to-dos What impact would it make? time...
2
Future consideration
6
VOTE
Separate permission for publishing to a KB
What is the challenge? Knowledge base content can be stored in the same workspace the product team uses to set strategy, track features, etc. However, just because someone has the ability to edit Roadmap data does not mean they should have the abi...
0
Future consideration
6
VOTE
Do not count description template as text when that field is required on idea submission
Who would benefit? Those utilizing the "template" option in description fields on ideas (and likely features) who have surfaced that field in portals and made it required. What impact would it make? Currently, if you have a template added for your...
0
Future consideration
6
VOTE
Ability to Configure Epic View as Default for all workspace views (Board / Prioritization)
Who would benefit? Enterprises who maintain Epic only or use Epic as primary record type. What impact would it make? Reduce confusion. The teams are currently directed to feature view on the board and prioritization view by default. Per Aha concie...
0
Future consideration
6
VOTE
Add "Dependency Not Scheduled" as a Delivery Risk
Who would benefit? Users who have enabled the Delivery Risks feature What impact would it make? It would allow to immediately capture on a feature if there is a dependency on a body of work that has not been scheduled. How should it work? Add a fu...
0
Future consideration
6
VOTE
Ability to send objects backwards/forwards in whiteboards instead of just to the front or to the back when layering multiple objects
Who would benefit? All Whiteboards users What impact would it make? This would enable users to easily order layered objects, which is particularly applicable when creating wireframes in the tool How should it work? Right now users can bring an obj...
1
Future consideration
6
VOTE
Ability to filter added/removed records in retrospective report
Who would benefit? Product managers trying to control churn within a release What impact would it make? It would enable us to more readily use this OTB report in change management of a release How should it work? We'd be looking for better general...
0
Future consideration