Custom field/status visibility dependant on portal

At the moment it is only possible to show/hide an idea status or idea custom field in all portals at once.

We would like to create a Public portal and a Private portal and:

- only display some ideas in the Public portal (status = Future consideration)

- only display some fields in the Private portal (field = Initial work estimate)

  • Marcin Mikołajczak
  • Sep 26 2016
  • Future consideration
Release time frame
  • Attach files
  • Adam Feldman commented
    December 13, 2017 21:28

    Use case

    • I have 2 idea portals: private/internal and public/external
    • The same products appear in both portals
    • I want the private/internal portal and ideas form to require our employees to enter data into a field which indicates the source of the idea (customer, partner, and/or employee)
    • I want the public/external portal to not make our customers do extra work to submit ideas
      • When our product mgmt team reviews ideas, they should be required to fill out the idea source field in order to save any updates to the idea
    • Currently, in Aha, custom field visibility is dependent on the product, not the portal, which doesn't enable this use case
  • David Bowen commented
    May 17, 2019 09:24

    I agree with this, we have exactly the same issue. Idea capture from multiple audiences is one of our key use cases. We're considering purchasing UserVoice instead.

  • Hannah Jackson commented
    July 12, 2019 17:14

    Functionality like this would also be exceptionally helpful at the user (groups) level, not just at the portal level.  For example, I want my A Team to provide more information than my B Team.  However, I want them to be using the same portal.  Requiring separate portal/URLs to manage who see's what us cumbersome for admins.

  • Ange Methot commented
    July 19, 2019 13:40

    Our use case is identical to that of Adam's where we have two portals (internal vs. external). As our internal portal collects additional information regarding customer data, size of deal, impact that we do not want as fields that are either requested OR visible to our external portal, we are forced to create duplicate ideas, OR to reduce the amount of useful information we are collecting that actually helps us manage, prioritize and rank the requests. 

  • David Bowen commented
    14 Jan 23:57

    Any information on when this is likely to happen?

  • Kris Zentek commented
    14 Feb 10:20

    I would very much like to see this too. My use case is that I want to provide a portal for different business units to submit different types of idea, all feeding into a single backlog. Customers and features, engineers and runway items, etc. Each would have different mandatory fields...

  • David Bowen commented
    05 Mar 16:11

    I thought this was planned, has it been pushed back to Future Consideration now?

  • Admin
    Kelly Sebes commented
    05 Mar 16:27

    Hi, David. We have a new feature coming in the next couple months that will cover some of the use cases described here. However, it will not cover them all so I set the status back to 'future consideration'. That way we will keep the idea open even after that new feature is available. More information to come soon!