# Voting in rows / Thumbs Up for entry **URL:** \ **Category:** Ideas & Features\ **Tags:** flexible-domain\ **Created:** [September 11, 2023, 7:27am UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114 "2023-09-11T07:27:04Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![Lukas\_Hroch](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lukas_hroch/32/6993_2.png) [@Lukas\_Hroch](https://community.fibery.io/u/Lukas_Hroch)\ **Post date:** [September 11, 2023, 7:27am UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/1 "2023-09-11T07:27:04Z")
In [Coda.io](http://Coda.io), we have used column „Thumbs Up“ for woting about features. I would like to have this feature in Fibery too. Maybe there is workaround how to achieve one member can vote one times for one entry 🙂 ![Snímek obrazovky 2023-09-11 v 9.23.32](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/d/d887079f39fc00a9348f5da51d5994b04e65f2a0.png) ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [September 11, 2023, 9:48am UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/2 "2023-09-11T09:48:35Z")
Voting is part of a Rating Widget functionality, see also > [@Rating Widget field type (showing total and average of individual ratings), e.g. Star rating, Thumbs up/down, Likes, etc](https://community.fibery.io/t/rating-widget-field-type-showing-total-and-average-of-individual-ratings-e-g-star-rating-thumbs-up-down-likes-etc/4983): > > Current User Experience Tensions and Limitations: In the existing Fibery setup, while we have powerful tools to capture and organize information, there’s a noticeable gap in capturing granular feedback. Single select fields, while useful, can only store one value at a time, making it challenging to aggregate feedback from multiple users or compute averages. This limitation hinders our ability to provide a holistic view of user sentiment, especially for project teams aiming to collect and analyze… ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 11, 2023, 11:00am UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/3 "2023-09-11T11:00:42Z")
> [@Lukas\_Hroch](#): > > I would like to have this feature in Fibery too. Maybe there is workaround how to achieve one member can vote one times for one entry 🙂 As I understand it, you are interested in collecting the votes from multiple users, and at the moment, the contents of fields in Fibery are not ‘per-user’. So there’s no simple way to achieve it. However, you could use buttons, combined with a user relation field to track support: Create a relation (many-to-many) between the Feature db and the User db, and call it ‘Supporters’. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a5049cd6a324b334590122a14ff78f2135aed315.png) Then, you can define a button automation (called ‘Vote for this Feature’) where the action is to link the user who pressed the button to the Supporters field. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/98b4c153a6a212d8434e4ec2df9adbac3dd2ed3e.png) With a formula field you can calculate the number of Supporters, and thus the popularity of the Feature. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3b638efc7367ca3553e60c082f8eb2f1c658e268.png) Note: if you want to limit the Users to only voting for max one Feature, create the relation as a one-to-many, i.e. a Feature can have many Supporters but a User can only support one Feature. ---
**Author:** ![Lukas\_Hroch](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/lukas_hroch/32/6993_2.png) [@Lukas\_Hroch](https://community.fibery.io/u/Lukas_Hroch)\ **Post date:** [September 11, 2023, 1:03pm UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/4 "2023-09-11T13:03:14Z")
Superb idea! I will try it. Thx ---
**Author:** ![Color\_Works](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/color_works/32/7614_2.png) [@Color\_Works](https://community.fibery.io/u/Color_Works)\ **Post date:** [September 12, 2023, 4:54pm UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/5 "2023-09-12T16:54:37Z")
Lukas, we have asked for this too! Please vote it up so we can get it! [[IN DEV] Improvements to comments](https://community.fibery.io/t/in-dev-improvements-to-comments/2741) ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [September 13, 2023, 7:23am UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/6 "2023-09-13T07:23:11Z")
Please note that comments reactions and this request are not related. To make voting right we have to add Reactions Field into databases, we discussed that and postponed the implementation. I can’t say when we will get to it so far… Soon we will have: - Reactions in comments. - Reactions block in rich text fields and documents. ---
**Author:** ![bear](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bear/32/12872_2.png) [@bear](https://community.fibery.io/u/bear)\ **Post date:** [September 13, 2023, 9:25am UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/7 "2023-09-13T09:25:27Z")
Thanks that is very useful! ---
**Author:** ![Color\_Works](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/color_works/32/7614_2.png) [@Color\_Works](https://community.fibery.io/u/Color_Works)\ **Post date:** [September 13, 2023, 2:42pm UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/8 "2023-09-13T14:42:39Z")
Outstanding and we are very excited about this! ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [December 23, 2024, 5:22pm UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/9 "2024-12-23T17:22:47Z")
> [@mdubakov](#): > > Reactions block in rich text fields and documents. I want to vote for this specifically. I’m trying to use the feed view more often and believe that this feature would be valuable for that purpose. ---
**Author:** ![Mircea\_Braescu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mircea_braescu/32/9729_2.png) [@Mircea\_Braescu](https://community.fibery.io/u/Mircea_Braescu)\ **Post date:** [February 17, 2025, 7:13pm UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/10 "2025-02-17T19:13:42Z")
This works nicely. Would it be easy to convert it into a toggle (and remove the vote if the user already voted)? ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [February 17, 2025, 7:51pm UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/11 "2025-02-17T19:51:41Z")
> [@Mircea\_Braescu](#): > > Would it be easy to convert it into a toggle (and remove the vote if the user already voted)? Yes, but it requires an extra field (can be hidden), and the button needs to use a formula to determine whether to add/remove the user who clicked. ---
**Author:** ![Mircea\_Braescu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mircea_braescu/32/9729_2.png) [@Mircea\_Braescu](https://community.fibery.io/u/Mircea_Braescu)\ **Post date:** [March 27, 2025, 8:24am UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/12 "2025-03-27T08:24:33Z")
This is available today with workarounds like the one Chris mentioned above. We’ve set this up for a particular entity type ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/6/6dc51c58b994bb00a533e9c8aee56dfe7a91f47d.png) ---
**Author:** ![Mircea\_Braescu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mircea_braescu/32/9729_2.png) [@Mircea\_Braescu](https://community.fibery.io/u/Mircea_Braescu)\ **Post date:** [March 26, 2025, 1:06pm UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/13 "2025-03-26T13:06:30Z")
One of the things that I miss from Confluence, and which would be useful here is reactions per entity / documents. Imagine you have a feed of announcements, or product updates, it would be great to have an easy way for people to react with emojis to it. Here is how Confluence does this for documents ![shot_250326_150347](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/2/2c2cc0d6c1193136bb16fd576b0b021c8a670e1d.png) and how it could be used in Fibery, for entities ![shot_250326_150439](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/1/1748a57e7d212f319734bdd182955072d09c7141.png) Without going too much into solution model, I could imagine this being as a unique type of field per database (just like comments and attachments are) ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [March 26, 2025, 8:22pm UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/14 "2025-03-26T20:22:48Z")
There is an existing feature request you can vote for: [Voting in rows / Thumbs Up for entry](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114) It includes this discussion: [Voting in rows / Thumbs Up for entry - #6 by mdubakov](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/6) ---
**Author:** ![Mircea\_Braescu](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mircea_braescu/32/9729_2.png) [@Mircea\_Braescu](https://community.fibery.io/u/Mircea_Braescu)\ **Post date:** [March 27, 2025, 5:44pm UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/15 "2025-03-27T17:44:15Z")
thanks I upvoted one of them that felt closer to my need ---
**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\ **Post date:** [June 26, 2025, 2:26pm UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/16 "2025-06-26T14:26:32Z")
I haven’t seen this mentioned here but wanted to add the idea of receiving public votes (reactions from non-users). I’ve been looking into how to host retrospectives with external parties in Fibery and it would be great to have a board view I can share publicly that allows everyone on the call to vote. That’s the use case Coda solved with their voting field ---
**Author:** ![gasby](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/gasby/32/11429_2.png) [@gasby](https://community.fibery.io/u/gasby)\ **Post date:** [July 25, 2025, 9:37am UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/17 "2025-07-25T09:37:12Z")
Commenting so that this gets more attention. This would be super valuable for the feed view. ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [July 25, 2025, 11:00am UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114/18 "2025-07-25T11:00:02Z")
I’m trying some workarounds - here a bit clumsy one but it works. At team level, there is a ‘template set’ of emojis. At user level, each user gets one set of emojis based on the template. Each emoji has many target entities (my thumbs up emoji is linked to all content that i gave a thubs up) ![msedge_PAXyqkPEPx](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/e0811ac56843dc8eacc7d9b1e90066b0947a4abd.gif)