RELATED IDEAS
Add multiple idea forms for same product
As a product manager, I must have the ability to accept enhancement requests from different stakeholders who have different types of information to provide, so that I can collect the right type of information needed to address the requirement.
We have internal stakeholders (consultants) who need to provide us with enhancement requests to replace customizations they have built for clients; clients typically are submitting requests for out of the box functionality for our product. We would like to have a separate portal for each group, with different available fields for them to provide us the specific detail needed in each different circumstance.
-
ADMIN RESPONSEMay 5, 2021
You can now create a different ideas form for each portal — so you can capture and show the exact details you want on each one.
Learn more and let us know what you think!
12
MERGED
Customizable idea form per portal or per user type
We have a need to have a different form for different types of users, one that asks for opportunity related information from partners and internal employees, and one that doesn’t from customers. As I understand it, there is no real easy way to do ...
0
Shipped
8
MERGED
15
MERGED
Providing different Ideas Portal submission forms
It would be beneficial to provide different ideas submission forms to different users of the system. An example would be requesting new ideas from internal developers versus customers. Internally, we might want to request different things than we ...
0
Shipped
© 2024 Aha! Labs Inc.•All rights reserved
Similar to others, this severely limits the ability of our org to use Ideas. We can have separate portals for employees and customers...but have to make both groups use the same form. They are different use cases . Employees can provide a lot more detail. For customers it needs to be quick and easy.
This would be extremely helpful for us. There is information we need to collect from internal users that we do not want to expose to our clients. And while internal users could create the ideas directly within Aha that is more complex workflow.
I also received this feedback (obviously hasn't evolved since 2017) to add a new product which is really bad practice. Our company is quite large and complex. We want to manage requests from multiple teams internally that are regionally specific (we operate in multiple countries with the same product)and from our customers and partners. The information we collect is not the same for these groups but they are all for the same product. Further in our use case we wouldn't want the ideas mixed together some of these internal requests are legislatively driven and require no voting (submittal only portal) but it would allow us to prioritize them and move them onto the roadmap. Really needed feature if Aha is to accomodate more complex products from an ideas perspective.
this is our #1 issue blocking our ability to launch to customers and partners.
This is a high priority feature for us. We'd like to create idea submission portals for external customers and internal stakeholders for the same product. Having to create a whole other product just to collect another product's feedback is an inefficient workaround.
Agreed: We want to be able to share the same idea objects across internal and external-facing idea portals, just with certain fields hidden or shown based upon the user class of each portal (think an internal employee idea portal and a customer-facing external idea portal). Otherwise we end up with a lot of duplicate ideas and lost opportunities for "me too" votes from individuals in their respective portals.
Creating different products just to collect a variety if input from different users is an inefficient manner to managing a product. It would be more beneficial to have the ability to target different users for a single product.