Conditional forms on ideas portal

Since I have more than one idea category, I have custom fields that are associated and useful for specific categories of ideas. Currently I need to put all of them on the input form and display layout for all ideas. This makes the form unnecessarily complicated, overwhelming and leads to confusion. I would like to be able to use conditional logic to display specific fields based on idea category or some other field. 

I would also like to be able to have a different version of the ideas portal for internal stakeholders vs. external users and customers; the latter group should have a much simpler view. So I would like to display certain fields based on user type, or better yet use different portals where I can expose a different set of custom fields in the layout.

  • Jonathan Berg
  • Dec 12 2017
  • Future consideration
Release time frame
  • Dec 20, 2017

    Admin Response

    Thank you for your idea. This is not currently planned on our roadmap but we will continue to monitor customer feedback here.

  • Attach files
  • Adam Feldman commented
    December 13, 2017 21:30

    See also APP-I-3170

  • Ron LeClair commented
    March 07, 2018 18:29

    Agree with this need 100%.   We also have multiple idea categories that require different custom fields.   It seems the segregation is almost there.   I can create separate portals but cannot have different entry forms or different custom fields display based on the category or the portal that I am in.

  • C Gordon commented
    March 26, 2018 18:32

    Agreed, we are starting with an ideas portal for internal users (pre-sales, sales, consultants, customer service) and we want to gather different information from internal user than from customers (once we roll-out the customer-facing ideas portal).

  • Ryan Matthews commented
    June 08, 2018 16:30

    I agree. This is something we would also benefit from and is becoming more of a need.

  • Kacie Hammon commented
    July 30, 2018 14:41

    I would love to see this.  I would like to create two custom fields with drop downs that are conditional...if you select this from the first drop down then you will see this is the second. 

  • Guest commented
    September 07, 2018 07:18

    All, 

    our need has some similarity here. We use categories to identify the product family to which the idea belong.

    Then in the Aha! tool itself we use customer field to provide more details about the product, like thetype of interfaces.

    I want to be able to show in the custom field only the interfaces that belong to the product family selected into the product categories field.

    Any workaround which allow to get the final result (like the model proposed by Jonathan) will be acceptable.

    Thx Riccardo

  • Laura Giles commented
    September 21, 2018 17:43

    Shouldn't status change to 'unlikely to implement'?

  • Devin Henderson commented
    December 31, 2018 03:40

    This is a MUST! I don't understand the need to have different idea layouts if you can't use them in different portals? Or why even allow multiple portals? Makes no sense.

  • Aha McTest commented
    January 30, 2019 12:54

    Very strange that multiple portals are supported, and there is robust customization, and multiple layouts can be defined, yet we can't design different forms for the different portals. 

    Along with public and private portals comes the need to expose public and private fields. 

    A public portal might just ask for a Title, Description, and Urgency

    A private, internal portal might ask for that, plus a Cost Estimate, Business Case, Segments to Benefit, etc. etc.

  • Michael Proctor commented
    April 26, 2019 14:37

    Most other 'forms' solutions, Microsoft, Google etc. support this with simple conditional inputs which drive users to different sections of questions, making the overall experience tailored for each user group but where there are a lot of shared fields. However Aha! is much stronger as an overall ideas management platform and especially with integration into a requirements management solution - please support this as it would bring feature parity and add a lot of value to your already great solution!

  • Steve Malpiedi commented
    April 26, 2019 17:48

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

  • Tom Esposito commented
    May 03, 2019 15:30

    Would also love to see this feature implemented

  • David Bowen commented
    May 17, 2019 09:32

    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.

  • Jens Kintrup commented
    June 13, 2019 10:22

    Full ACK would be great to see this implemented.

  • Guest commented
    October 24, 2019 12:27

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

  • Dan Jeffery commented
    October 30, 2019 11:41

    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.

  • Liz Owens commented
    November 06, 2019 17:50

    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.

  • Dan Jeffery commented
    10 Feb 09:54

    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.

  • Dustin Ingram commented
    06 Mar 17:11

    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.

  • Carlton Hightower commented
    20 Mar 22:13

    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.