Ideation programs can be intimidating, and many community teams shy away from implementing them. Sometimes, it's because they feel they won't get buy-in from the Product team, or they think the initial support will eventually fade away. Especially in large communities, teams may also fear receiving a high volume of ideas that simply don't align with business objectives or are unrealistic. Managing that at scale can become quite cumbersome.
Fully open ideation programs are great and can generate significant value for both community members and business stakeholders if teams are aligned, there is proper buy-in from the Product organization, and ideas — along with their statuses — are managed appropriately. However, the reasons mentioned above for why some community teams choose not to create such programs are valid, and it is always preferable not to have an ideation program than to have a non-functional one in place.
