The discussion addresses usability issues with selecting subcategories in the Kanban Topic Customizer (TC), where users must manually enter the subcategory slug without the parent path. nathank notes that this non-intuitive behavior differs from other TCs and has updated the documentation to clarify that only the subcategory slug (e.g., requests-roadmap) should be used, excluding the parent slug.
While aidanheerdegen initially struggled with formatting, they discovered that slugs may contain dashes instead of underscores. However, Discoursenaut reported issues setting up a default view for a specific subcategory. After nathank corrected the specific slug to roadmap, Discoursenaut confirmed it still did not work, suggesting a potential limitation of the plugin rather than a user error. The thread concludes with a suggestion that the TC would benefit from a proper category selector interface.
At the moment you cannot intuitively specify having a Board active on subcategories. The setting itself doesn’t offer guidance or give a selection.
In order to select a subcategory, you need to enter just the slug of the subcategory (without the parent slug). I think that this is a bit unique within the Discourse UI, and is different to most other TCs. This trips up quite a few people it seems.
I can’t get them to work for my subcategories. How did you configure your subcats? Using something like category/sub_category where all lowercase regardless of display case?
To answer my own question, this is covered here
and though I played with some combinations, I didn’t get the right one, which is to use the correct slug (underscore had been translated to a dash) and for category and subcategory to both be included, separately without any path in the subcat.
I’m trying to set up the default view here: Roadmap - Bitwarden Community Forums
and entered feature-requests-roadmap into the ‘default view’
it doesn’t show up as a board by default, any suggestions?
I think you just use requests-roadmap to achieve that!
I’ve edited the Kanban Board settings documentation to make this a little more obvious by adding this:
For subcategories, don’t include parent slug.
It would be nice if this TC used a proper category selector instead, but it does work fine once you’ve worked this out!
Thanks for the tip! I tried your suggestion and ‘feature-requests-roadmap’ but neither did the trick.
Just looking at your site again - I misread your subcat slug sorry. The link of your subcat:
https://community.bitwarden.com/c/feature-requests/roadmap/81
This means that you should actually simply use roadmap.
Thanks for following up, I did try that but it did not work, maybe just running up against a limitation of the plugin.