# Add Tag Group support to Discourse integration

**URL:** <https://community.fibery.io/t/add-tag-group-support-to-discourse-integration/2201>\
**Category:** Integrations\
**Created:** [November 10, 2021, 4:06am UTC](https://community.fibery.io/t/add-tag-group-support-to-discourse-integration/2201 "2021-11-10T04:06:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [November 10, 2021, 4:06am UTC](https://community.fibery.io/t/add-tag-group-support-to-discourse-integration/2201/1 "2021-11-10T04:06:59Z")

</div>

Now trying to use Discourse integration in production a forum with 1000 posts and 1500 users, and finding another limitation: no support for Tag Groups. The failure outcome is quite problematic, like: [Sub-categories not synced in Discourse integration - Category becomes blank!](https://community.fibery.io/t/sub-categories-not-synced-in-discourse-integration-category-becomes-blank/1950). I.e. the tags just don’t show up when they’re in groups. 😑

Please add Tag Group support to the integration as soon as possible!

> **[How to create tag structures, tag category restrictions, tag groups and tag...](https://meta.discourse.org/t/how-to-create-tag-structures-tag-category-restrictions-tag-groups-and-tag-relationships/48260)**
>
> Now that tag support is a core feature of Discourse instead of being a separate plugin, we’ve added some new features around tagging. In this How-To I’ll go through setting up a tag schema like Car Talk uses. We’ll want to achieve these things: ...

This and lack of sub-category support are more or less dealbreakers for our forum in real-world use. You can’t expect us to reconfigure/restructure our entire forum just to make this work. And so, as I mentioned in another thread about the Discourse integration limitations: have you considered that the reason the Discourse integration is not much used is it’s just **kind of broken** for real-world use-cases? OK, OK, I know Fibery team itself uses it, but then… you’re not the most sophisticated users of Discourse, it must be said 😄 (no disrespect intended!). Though I’m still actually mystified that the lack of sub-category support hasn’t been solved since you yourselves use them…

In practice _many_ real-world teams that actually use Discourse would not be able to properly make use of the integration to manage their work, e.g. Figma (tag groups), Airtable (tag groups + sub-categories), etc. Actually, I wonder if @karthikk_vijay is still around: RemNote uses sub-categories and I’m curious if this has been a problem for them, or if they just didn’t end up adopting Fibery.

In any case I hope this and sub-category support can be addressed sooner than later. I know they’re not overall priorities, but my sense is they should not be a lot of work, so hopefully they can be wedged into a release in the near future…
