Conditional forms on ideas portal

I agree that this should be available for the Enterprise+ plan.

This is great however for Enterprise+ plan this is not helpful. It means i need to purchase this

I'd really like to see conditional field logic in my initiatives layouts - it would be wildly useful there in ensuring that teams only see the fields they need, making the product far more useable and ensure better data overall.

Big thumbs up on this one from my internal customers. Conditional logic would improve idea submission and routing for everyone across the idea lifecycle. Glad to see this has moved to Future Consideration!

I would love to see this option added to Aha. At the moment we create create requirements and based on the type the next steps vary. At the moment we need a large choices list to cover all the options which is confusing for our users

Yes, still a market need.

if this would make it possible to create branching in idea submission form, I am all for it. Making it possible to dive deeper on idea forms by adding branching questions is a need I have today.

yes, please add this a higher priority. We are beginning to use intake forms and discovered we can only have one form for each workspace. We have a use case where we have 7 different forms, depending on request type. We now have to restructure to create a parent line and 7 workspaces just to accommodate the different ideas forms.

With more and more custom fields being used to capture relevant product data, the need for conditional fields is high.

This would be huge for us.

This proposed feature would benefit the collection of additional idea feedback that would enhance the detail submitted for roadmap consideration. It would reduce the amount of back and forth discussions about the idea and keep the associated information with the idea where it belongs.

definitely agree that a big benefit to having multiple portals in a workspace is access to different audiences but even more to be able to solicit different information from those different parties. this idea has been out there for a while. would love to see this implemented.

Bumping this to try and get some focus from the Aha team. The Aha adoption from our 150+ sales team has been great. As a result they are pushing the Product Management team to use the portal for requirements capture on various topics. Because of the technical nature of our business, our current portal form is very bespoke and calls for a lot of mandatory information. We can use categories to make the requests more focused but regardless of the ask the form remains the same and becomes totally irrelevant in most cases. This means that we would currently have to add another portal for these requests just becasue we need a simplier form. Our response to the sales teams at the moment is "Aha doesn't support us being able to use the portal for different requests where different information is needed". This is not good press for something that is deemed as basic functionality across many applications.

Ditto those who have said this is a need as we go forward with our plans to roll out ideation within Aha!.  Someone in our working group expressed that a lack of this feature is like working in the last century. I've used it in other ideation platforms for years. I know Aha! is more than ideas, but ideas impact our roadmap.

We are in desperate need of this. Please can you provide an update... rasied nearly 2 years ago with 84 people voting and 15 comments... Clearly this is something that the Aha community are in need of.

Has there been any change with the roadmap and consideration for this functionality since 2017?

Full ACK would be great to see this implemented.

I agree with the aspect of having different fields displayed for internal vs external audiences. Idea capture from multiple audiences is one of our key use cases. We're considering purchasing UserVoice instead. See also: APP-I-4184, 3170 and 5433.

Would also love to see this feature implemented

Can you provide an update on this? Has anything changed since 2017?