# Upgrade Discource Features to include voting, tagging **URL:** \ **Category:** Ideas & Features\ **Created:** [August 31, 2020, 4:14pm UTC](https://community.fibery.io/t/upgrade-discource-features-to-include-voting-tagging/938 "2020-08-31T16:14:09Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\ **Post date:** [September 14, 2020, 6:32am UTC](https://community.fibery.io/t/upgrade-discource-features-to-include-voting-tagging/938/2 "2020-09-14T06:32:20Z")
Love this request @helloitse, was going to in fact post myself something like this and I found it! A lot of the other up-and-coming tools out there allow the ability to vote-up features. Some have it in Discourse, off the top of my head: - AirTable - Asana - Monday And ClickUp famously does this, but in another tool Canny and I think that has gotten out of control more than they bargained for… I agree we have dup requests in here, and may basic requests around things like “recurring Tasks” that kick around in various places, and it would be great just to see the simple request, votes, and possibly see Team Fibery responses as to when we could expect that stuff. This forum is great, I think you guys have Coda and Notion both beat with more real commentary around what you’re planning, but as users and feature request grow, I think this organization is really essential. The reason I was going to request this is I’m myself having some trouble trying to figure out what’s really a Fibery priority, and what isn’t. Things that have been discussed, that would be great for my use, but remain vague as to their delivery: - Multiple-State Kanban: > [@Kanban board details - WIP Limits](https://community.fibery.io/t/kanban-board-details/328/3): > > Thanks @mdubakov. Our primary need for Fibery is to be able to improve our work management overall, in a real way, by really considering “lean” principles and the core concepts of kanban. One of the problems we have is people focusing on too many tasks and trying to multitask, which is for most people super inefficient. If we can control the WIP even in a soft way, it acts as an everpresent reminder to focus, and to not multitask. We have a formal way of capturing support request tickets, but, t… Key stuff like WIP, Cycle Time, etc. - Activity Stream: > [@\[APPROVED\] Activity Stream](https://community.fibery.io/t/activity-stream/109): > > A dedicated page for all key user activities aggregated from user selectable “spaces”. What type of activities get listed can be configurable. Any @mentions should be highlighted too in this activity feed. really hard for me to function without this - Phone # type > [@\[DONE\] Phone number field/extension](https://community.fibery.io/t/implement-phone-number-field-extension/439/4): > > Hey @helloitse I really second the sentiment about using Fibery for a CRM. The capability is here, we have the API and Vizidrop as great supplements too - for import of data and analysis, respectively, that the other nocode stuff can’t duplicate. Definitely the phone # data type would be key though to make this work! Not sure what complexities are here, but I’d surely add my vote, and nothing from Fibery team since 2019. And there are many other examples. Thanks! --- _[View the full topic](https://community.fibery.io/t/upgrade-discource-features-to-include-voting-tagging/938)._