# 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:** 8

<div class="post-metadata">

### Author: ![chapoi](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chapoi/32/537252_2.png) [@chapoi](https://meta.discourse.org/u/chapoi)
#### Post date: [August 13, 2025, 11:39am UTC](https://meta.discourse.org/t/categorizing-bug-and-ux-issues/378121/8 "2025-08-13T11:39:59Z")

</div>

> [@sam](#):
>
> I guess one alternative is to simply have stuff live in feature/bug unconditionally and use tags to denote ux.

I like the idea of ux as a tag (and maybe have dev as a tag too?) , but I agree that there could be UX cases that feel like they don’t really belong in a different category either.

And some topics may be technically a feature, but are so small, that they would feel out of place in the feature category to vote on, for example: [Clickable components instead of just the Edit button](https://meta.discourse.org/t/clickable-components-instead-of-just-the-edit-button/378397)

But maybe we shouldn’t care? And any issue that asks to change something does belong in the feature category, no matter how small?

Or maybe we should have a category “Suggestions” – for things that aren’t broken, aren’t a full-blown feature request, and aren’t about how to do things. And then we can tag it dev or ux internally.

Edit: realised we already _have_ a ux-tag, it’s just under utilised atm

---

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