# 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:** 4
### 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 12, 2025, 9:49pm UTC](https://meta.discourse.org/t/categorizing-bug-and-ux-issues/378121/4 "2025-08-12T21:49:49Z")
Some thoughts from my side: - I believe that dividing over 3000 topics into just 2 categories is a lot of work, and I wonder who will have the time to take on this task. - Furthermore, I do not believe that all topics in UX can be easily divided into Feature and Bug. For me, a report about a text that cannot be translated is not really a bug report\[1\]. Likewise, pointing out an incomprehensible or outdated text is neither a feature request nor a bug report\[2\]. Similarly, descriptions of user experiences that contain neither an error nor a concrete improvement suggestion do not fit into Feature or Bug\[3\]. - I do not know how you have handled this so far, but I had the impression that developers, when necessary, also worked on UX topics, and vice versa. I wonder whether it might be possible to keep things as they were, with the group monitoring the category simply informing the other group if needed, without moving the post. However, I cannot fully evaluate this, as I do not know the processes before or now. * * * 1. [example](https://meta.discourse.org/t/badges-form-section-titles-are-not-translatable/342200) 2. [example](https://meta.discourse.org/t/sidebar-show-upcoming-events-setting-description-needs-an-update/331443) 3. [example](https://meta.discourse.org/t/confusion-with-saving-edit-of-query-name/345885) --- _[View the full topic](https://meta.discourse.org/t/categorizing-bug-and-ux-issues/378121)._