Allow default setting of Ideas created in the main Aha screens to be configured as the default is Not Visible in the Ideas Portal

I'm adding another vote. The admin response does not address the problem because giving users a dropdown they have to understand and remember to use isn't a solution. The ability to customize the create form solves other problems, but it does not solve the issue of having ideas default to not being visible.

We too use the main Aha! platform to submit ideas- similiar to the use cases described below it is natural to forget to change the visibility to all. Right now, I run a weekly report to see what Ideas are not visible and I manually change the visibility. I'd like to remove this manual step as it will not scale.

Hi, yes I am with Ryan. While the ability to set the default visibility in the idea creation form is a useful workaround to at least give the submitter a chance to set visibility, too many times it is skipped over and the idea doesn't appear in our various portals. It would be really helpful to be able to set this default value to reduce the manual steps our PMs have to remember to do.

I'd like to bring this up again if possible. Our internal PM team likes to create new ideas using the main Aha platform instead of the portal. This is primarily because we can easily give the custom fields values which we don't expose through the ideas portal. However, people naturally forget to change the visibility setting so we end up with ideas that are not visible through the portal and can't be voted on externally.

Any thought to considering this again?

The premise that it is enough to give the ability to set the visibility using a custom form from the main portal is flawed for a couple reasons:

1. If the desired default is other than the you're defined behavior, it is onerous to require the users to set this every time they create an idea.

2. There are other flaws in Aha Ideas that have pushed us to enter more ideas via the main portal, thus making the problem here that much worse.

In our case, the fact that you do not allow custom fields to be shown in the Idea creation process via the ZenDesk integration has pushed to move to the model where support agents create their tickets via the Aha portal, then go back into ZenDesk to link the ticket to the case. This is not possible to do given the defaults you have set. Just adding the field adds one more barrier to addoption. Between the flawed implementation of your ZenDesk integration and now the fact that you're not allowing visibility defaults to be set for portal created Ideas, it's becoming unclear if Aha is the right choice for my company to use for Ideas.