# Feature to allow uservoice/getsatisfaction suggestions and voting **URL:** https://meta.discourse.org/t/feature-to-allow-uservoice-getsatisfaction-suggestions-and-voting/19812 **Category:** Feature **Tags:** completed **Created:** [9월 9, 2014, 12:15오후 UTC](https://meta.discourse.org/t/feature-to-allow-uservoice-getsatisfaction-suggestions-and-voting/19812 "2014-09-09T12:15:59Z") **Posts on this page:** 1 **Showing post:** 6
### Author: ![cregox](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cregox/32/115904_2.png) [@cregox](https://meta.discourse.org/u/cregox) #### Post date: [9월 30, 2014, 5:02오전 UTC](https://meta.discourse.org/t/feature-to-allow-uservoice-getsatisfaction-suggestions-and-voting/19812/6 "2014-09-30T05:02:43Z")
What you mean by either or both those “custom views”? From my weak perspective, sorting is all we need. Token isn’t necessarily a good idea. On a similar note, I’m thinking about using discourse as it is for ticket support (one of the other 2 aspects from uservoice): > [@Using discourse as a community ticket system](https://meta.discourse.org/t/using-discourse-as-a-community-ticket-system/20607): > > I understand we should probably not use discourse for this, but what if I want a new kind of “community open” ticket system? Can you picture any deal breaker issues with this? Also, is there maybe someone else who tried to do anything similar? Without any extensibility, this is how I envision it might work right away, for our little business: We’d slowly and even personally warn users of how it works. They’re already used with our different thinking methodology anyway. Anyone would be able t… --- _[View the full topic](https://meta.discourse.org/t/feature-to-allow-uservoice-getsatisfaction-suggestions-and-voting/19812)._