# Searching for status:unsolved returns topics from non-solution enabled categories

**URL:** <https://meta.discourse.org/t/searching-for-status-unsolved-returns-topics-from-non-solution-enabled-categories/267700>\
**Category:** Bug\
**Tags:** search, solved\
**Created:** [June 8, 2023, 3:13pm UTC](https://meta.discourse.org/t/searching-for-status-unsolved-returns-topics-from-non-solution-enabled-categories/267700 "2023-06-08T15:13:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dandv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dandv/32/169779_2.png) [@dandv](https://meta.discourse.org/u/dandv)\
**Post date:** [June 8, 2023, 3:13pm UTC](https://meta.discourse.org/t/searching-for-status-unsolved-returns-topics-from-non-solution-enabled-categories/267700/1 "2023-06-08T15:13:35Z")

</div>

Our forum has `allow solved on all topics` disabled, and the [Support](https://forum.weaviate.io/c/support/6) category with **Solved** enabled and the drop-down filter working correctly.

The problem is that a [search for `status:unsolved`](https://forum.weaviate.io/search?expanded=true&q=status%3Aunsolved) still includes results from categories that have `Allow topic owner and staff to mark a reply as the solution` unchecked (for instance [Showcase](https://forum.weaviate.io/c/showcase/5) where “Solved” doesn’t quite make sense).

Is this a bug? Should that query only show unsolved topics across categories that have **Solved** enabled, but instead it looks for the absence of the “solved” attribute?

(As a workaround I tried searching for `status:unsolved #support #general`, these being the categories that might have **Solved** on, but that returned zero results because [searching across categories isn’t implemented yet](https://meta.discourse.org/t/allow-searching-across-multiple-categories/98045).)

---

<div class="post-metadata">

**Author:** ![pmusaraj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pmusaraj/32/119489_2.png) [@pmusaraj](https://meta.discourse.org/u/pmusaraj)\
**Post date:** [June 8, 2023, 4:34pm UTC](https://meta.discourse.org/t/searching-for-status-unsolved-returns-topics-from-non-solution-enabled-categories/267700/2 "2023-06-08T16:34:03Z")

</div>

> [@dandv](#):
>
> Is this a bug? Should that query only show unsolved topics across categories that have **Solved** enabled, but instead it looks for the absence of the “solved” attribute?

Yes, I think you’re right, this is a subtle bug. When searching for `status:unsolved`, we should only list topics in categories where topics can be marked as solved.

We will work on a fix over the next few weeks.

---

<div class="post-metadata">

**Author:** ![pmusaraj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pmusaraj/32/119489_2.png) [@pmusaraj](https://meta.discourse.org/u/pmusaraj)\
**Post date:** [June 20, 2023, 5:57pm UTC](https://meta.discourse.org/t/searching-for-status-unsolved-returns-topics-from-non-solution-enabled-categories/267700/6 "2023-06-20T17:57:13Z")

</div>

This should be fixed now @dandv, per [FIX: Search bug for status:unsolved returns topics from non-solution … · discourse/discourse-solved@4032a1e · GitHub](https://github.com/discourse/discourse-solved/commit/4032a1e35f4cf6a42b5cbedd780e8344dc442346), thanks @Juan_David_Martínez for the fix.

---

<div class="post-metadata">

**Author:** ![pmusaraj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pmusaraj/32/119489_2.png) [@pmusaraj](https://meta.discourse.org/u/pmusaraj)\
**Post date:** [June 22, 2023, 5:57pm UTC](https://meta.discourse.org/t/searching-for-status-unsolved-returns-topics-from-non-solution-enabled-categories/267700/7 "2023-06-22T17:57:22Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.