Hi all, we're considering releasing a different version of tags we'd call "Categories". They would be completely separate to tags and would be public facing.
– Categories are created by admins on a board level
– Users can optionally specify a category when creating a new post
– There is a limit to one category per post
– Admins can change a post's category at any time
– Admins can subscribe to the categories they care about to get those posts in their admin report
We'd love to hear your thoughts. Would this be helpful for your team? Please leave a comment or message us directly!
@Sarah Hum: Yey! Exciting to hear that a form of public-facing organization is coming! I'm really looking forward to this! I've tried to use tags, but just never really felt the value in doing it since it wasn't public facing.
Almost all of my tags are features of my product. Personally, I'll probably stop using tags and just move all my tags into categories, since I prefer public-facing categorization. (Though I'm a one-person team, so maybe other teams find use in admin-only tagging.)
I think it will work pretty well for my use case, but I do see some minor issues I might run into with categories being public rather than tags. For example, I tag everything with a feature, and in some cases, I'll tag it with a platform too, such as "Web" to make it clear that it's a web-only feature request. This would be helpful for people who are wondering what features are coming to web. I might just put "[WEB]" in the title since the majority of posts are not platform-specific.
There might be some posts that would fall under two features, but the majority should be fine fitting into one. I can probably fit them into the the more logical one if that happens.
Thanks for the thoughts @Dan Leveille! We're leaning towards one category per post for simplicity for your users. We find that the more complex we make it to give feedback, the less you'll get. We want to keep potential confusion to a minimum.
This would be very appreciated! If you do it, will the creator of a new feature be able to choose among tags created by the admin? And will it be a setting to decide if the users should be able to create new tags or not?
I don't have a problem with this SO LONG as there's the option to do so. We do not want our end users seeing tags.
@Drew Libin: Hey Drew, definitely not to worry. If we do make improvements here, we won't all of a sudden make all your tags public. They'd stay private.
Would love to have this. It'll make things easier to group together for our clients.
Would love this!
@Andrew Rasmussen we would prefer only a public/admin combined to be able to tag based on modules or functions. Sometimes feature requests are specific to a small function/module and even we started a week ago we see clutter....
We'd like to be able to set tags as Admins, and allow Users to select one or more existing tag(s) to categorise their post.
That will allow us to quickly filter requests into "buckets" and group by type, product/area etc.
To generalise the functionality, you could have the option to allow user creation of tags so it's either pick-from-existing or pick-or-create
We would like our voters to be able to filter on [tags] from public view. Currently this is only available in admin view. We have this need since we have colleagues internally that would like to see status on the posts that are relevant for them, eg a specific [tag]. They would like to do this on board level, but also to be able to query across all boards.
I think tags are intended to be used for an internal use only. If you make this feature available, please let an option to keep tags private, since this would become an issue for us.
@Andrew Rasmussen: 🤗
@Vincent from CrakRevenue: Hey Vincent, if we do make tags public, we'll definitely have a privacy option, with existing tags private by default. Not to worry.
@Andrew Rasmussen: Nice - I'm going to use these to be able to categorise feedback types that ONLY we would want to see i.e. Prevent Churn, Compliance, Sales Opp etc.
Strikes me that it simply needs internal/external tags. A hybrid of these could be fairly horrible to manage of there are lots remembering on ALL board to ensure the same tags are private.
It would be good to include the ability for user to be able to filter by tag once they have been made public.