# Categorizing bug and ux issues

**URL:** https://meta.discourse.org/t/categorizing-bug-and-ux-issues/378121
**Category:** Site feedback
**Created:** [August 11, 2025, 9:12am UTC](https://meta.discourse.org/t/categorizing-bug-and-ux-issues/378121 "2025-08-11T09:12:05Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![Moin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/moin/32/554653_2.png) [@Moin](https://meta.discourse.org/u/Moin)
#### Post date: [August 11, 2025, 9:12am UTC](https://meta.discourse.org/t/categorizing-bug-and-ux-issues/378121/1 "2025-08-11T09:12:05Z")

</div>

> [@Footnote doesn't disappear when you click a link inside](https://meta.discourse.org/t/footnote-doesnt-disappear-when-you-click-a-link-inside/377627/2):
>
> small administrative note.
> 
> Even though this is technically UX, generally UX is what our designers triage, and in this case the bug is in the hooks footnote has into the Ember router. (or is missing)
> 
> So the fix here is going to need an engineer.
> 
> Moved it to bug and alerted the right engineer, we should get is sorted in the next few weeks.

> [@Themes don't appear on themes page without reload after install](https://meta.discourse.org/t/themes-dont-appear-on-themes-page-without-reload-after-install/378119/2):
>
> Moved this to #bug::category because eventho it’s visual and not really broken, our UX (designers) won’t be able to fix this.

It feels a little weird to choose a category based on “who is most likely to fix it”. Would you also say a blank forum because of a global `display: none` isn’t a bug because a designer will fix it?  
And of course you can say “it doesn’t matter, simply select one, we can move it” but this only helps for posting. When I try to find prior reports I would search for both of these issues in #Contribute > UX. Would it be possible to track responsibility for fixing independently from categories?

> **[Bug](https://meta.discourse.org/c/contribute/bug/1)**
>
> A bug report means something is broken, preventing normal/typical use of Discourse. Do be sure to search prior to submitting bugs. Include repro steps, and only describe one bug per topic please. If your topic is about an official plugin, include the plugin tag.

> **[UX](https://meta.discourse.org/c/contribute/ux/9)**
>
> UX topics are used for when Discourse technically works as intended, but the design, interaction, or flow creates unnecessary friction, confusion, or inefficiency for users. Also for small “quality of life” improvements. completed or fixed tags are applied depending on the nature of the topic.

---

_[View the full topic](https://meta.discourse.org/t/categorizing-bug-and-ux-issues/378121)._