Skip to main content

Consider omitting "completed" entries from search results by default

Requests & Insights

Most of the time, when I’m searching posts, I’m doing so to determine whether a specific feature request or bug already has an associated post or not. I imagine many people (or users at least) have the same intention. With that, it would seem to be a better UX to omit “completed” posts by default.

Screenshot of the current situation, in which my recent search yielded a “completed” post as the first result.

Post type
✨ Other
What part?
Feedback portal, Dashboard
Posted by Luke M ·
3 comments

Log in to comment and vote

Comments3

  • Product team

    •

    Feb 22

    Customers also find this very frustrating. They are looking for their posts and find hundreds of done posts. Thus they want to automatically omit “completed” to their search filter by default

    • Luke M

      •

      Feb 22

      Thanks for the comment, I’m grateful that this is on the product radar!

  • Luke M

    •

    Jul 12, 2024

    Some additional context (since I apparently can’t edit a post after submitting it):

    On further inspection, I find it particularly cumbersome that the search filters are all unchecked by default—thus, if I want to filter out only the “completed” posts (and related things like “duplicate”, “already exists”, etc), I need to click about 7 times (checking all the options except except those I wish to filter out. I would expect the filters to all initialize in the “checked” state, at the very least.