Skip to main content

Ideas can have different ideation status that we can define in Control. At least one status in every ideation process is “closed” (or something like that, e.g. “duplicate”), meaning, that an idea - in one way or another - will not be further pursued.

That’s why we propose an option to disable voting for any given ideation status. This way users can’t vote for ideas with this status anymore.

If voting stays enabled, even though an idea is “closed”, it can cause user frustration and can also put unnecessary pressure and additional work on the community team when “closed” ideas still get votes.

 

@Kenneth R asked me to post a new idea about the possibility to disable voting on merged idea (=ideas that have the status “Duplicate”). But I saw this idea by @bjoern_schulze and this seems to be the same thing!

What I am suggesting is the possibility to disable voting when an idea has a certain status and/or the ability disable voting in general :)


Thank you @Suvi Lehtovaara - your inSpired searching skills were clearly superior to mine yesterday.  :D 


I want to add something to this idea! I think it would be great to enable and disable de voting of the idea. We want to people can share their ideas 2 months, for example, but you can only vote the last two week. So then we will enable the voting part. Can we do this?


The following idea has been merged into this idea:

All the votes have been transferred into this idea.

Updated idea statusOpenAdded to Backlog

Yes, please! Voting for statuses such as Merged, Completed or Declined does not make much sense. It would be great if we can configure this per status.


The following idea has been merged into this idea:

All the votes have been transferred into this idea.

The following idea has been merged into this idea:

All the votes have been transferred into this idea.

Our Product Managers have asked us for this as well! It would greatly help our integrations with ideation and reduce the number of unnecessary reminders and pings. Thanks for your consideration!


We just migrated from another platform where we had this -- was super helpful to have especially as different use cases/edge cases or reasons for not doing something pop up!