Custom field/status visibility dependant on portal

I also agree with Adam D that the Proxy vote function does not address this request. We have the exact use case scenario as Nico van Wijk. For ideas raised by our internal staff we want to capture & display additional information that we do not want to expose to our clients. We don't want to use comments as it is specific pieces of information that we then want to report on etc. The use of voting does not solve this at all.

I agree with Nico van Wijk and other commenters and disagree with the Admin response as the Proxy vote function does not address this request. The idea is to allow different portals to have different form layouts. Currently the only way to achieve this is to create multiple workspaces which seems quite clunky.

I can see that this idea has been registered in 2017. Is this going to be evaluated? We are quite surprised that only one idea portal layout can be supported per workspace, but you have the ability to have more idea portals. Our use case is to have internal ideas and customer ideas and these will be registered each on their own portal.

What also would be a great improvement is to be able to set fixed filters based on (custom) fields to which ideas within the workspace will only be visible on the idea portal.

Dont think Proxy Votes will help us either. We have Sales involved early on with deals that they are working and they need to get an Idea in for a potential customer. They are not a real customer yet and thus wouldnt have any Ideas users to which to use a proxy vote on.

We want an internal portal and an external portal and the ability to have different custom layouts for the Ideas based upon the portal.

Agree with David. Another only way of 'fudging' this is to use separate Products per Portal which is not practical. Proxy voting is OK when the idea initiates from a customer but we need the ability to initiate the idea internally. If creating ideas direct in Aha, you lose the capability of surfacing like-minded ideas, which the portal has.

Proxy voting doesn't help either of these uses cases. We could move to enabling proxy voting however the core problem still exists, which means we can't use this feature outside our organization. We need the ability to hide certain fields from public view on the public portal, while maintaining them as visible on the internal one.

Hi Katha and Joey,

Thanks for the response!

Would you be able move the 'internal only' fields from the ideas form to the new proxy voting form? Your ideas form would then only have fields that are appropriate for all users, including customers. The proxy voting form would only be enabled in an internal portal, for capturing the additional information that you need from your own teams.

Sorry, I don’t think that this really supports the use case that many of us here have described. We already capture customer and partner related requests from our own teams and tag it with related customer etc. We want an external public portal so that we can remove this step in the process and get an unfiltered flow of requests from our users. Not just requests that more motivated internal teams are sharing. We are considering Uservoice or possible other solutions for this but would prefer not to have to start capturing this in multiple different systems.

We have internal idea portal that requires requires additional fields such as customer information and other internal data, and these fields are not not applicable to customer facing portals.

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!

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

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...

Any information on when this is likely to happen?

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. 

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.

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.

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