# Inconsistent marking of Topics as ☑️ Solved, Completed, or Fixed here on meta.discourse.org

**URL:** https://meta.discourse.org/t/inconsistent-marking-of-topics-as-solved-completed-or-fixed-here-on-meta-discourse-org/361193
**Category:** Site feedback
**Created:** [April 10, 2025, 3:11am UTC](https://meta.discourse.org/t/inconsistent-marking-of-topics-as-solved-completed-or-fixed-here-on-meta-discourse-org/361193 "2025-04-10T03:11:25Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [April 15, 2025, 5:31pm UTC](https://meta.discourse.org/t/inconsistent-marking-of-topics-as-solved-completed-or-fixed-here-on-meta-discourse-org/361193/8 "2025-04-15T17:31:27Z")

</div>

Gosh. You made that sound complicated. 🙂

Ostensibly, you pop the #fixed tag on bugs that have been fixed and #completed on feature requests that have been implemented. \[1\] It’s part of the process to close the topics out (and keep interested parties updated with the relevant info). They were initially implemented to provide some visual indication that ‘a good thing had happened’ versus the lock symbol of a closed topic. When these tags are consistently applied you get a nice wave of green when you scroll down their category topic lists.

(And #delivered was a separate but similar one that wasn’t team—controlled so it could be used in #Marketplace)

For Solved, there are quite a few categories where it’s active rather than just the generic #Support category. Pretty much any category where the majority of topics are going to be questions that can get a solution. #Support, #installation, #Development, #data-reporting, #Support > SSO

Ideally, the best practice is to have the OP mark the solution but we know that this sometimes doesn’t happen (for a variety of reasons) so I would often scroll the topic lists back and clean some outstanding ones up after a couple of weeks or so (once they were deemed to be ‘abandoned’)

> [@tobiaseigen](#):
>
> There was one topic, [“Reader Mode” theme component feedback](https://meta.discourse.org/t/reader-mode-theme-component-feedback/304314), that was in #site-feedback::category but I’ve now moved it to #Customization > Theme component where it seems to belong now that the component has been released.

FWIW The #Customization > Theme component topic for that is [Reader Mode](https://meta.discourse.org/t/reader-mode/307916), so really that #feedback topic you linked shouldn’t be in #Customization > Theme component (as it’s not a theme component topic). It should probably be in #Contribute > Feature or #Contribute > UX as I think that’s where these have come to live now more of them exist.

(I think it was in #Contribute > Site feedback as it was an experiment here on meta)

* * *

1. and with #Contribute > UX being a halfway house between the two either can be used depending on the ‘flavour’ of the specific topic

---

_[View the full topic](https://meta.discourse.org/t/inconsistent-marking-of-topics-as-solved-completed-or-fixed-here-on-meta-discourse-org/361193)._