# Inconsistent meaning of Yes/No actions in the review queue

**URL:** https://meta.discourse.org/t/inconsistent-meaning-of-yes-no-actions-in-the-review-queue/404418
**Category:** UX
**Tags:** review-queue
**Created:** [June 3, 2026, 12:26pm UTC](https://meta.discourse.org/t/inconsistent-meaning-of-yes-no-actions-in-the-review-queue/404418 "2026-06-03T12:26:08Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![sableraph](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sableraph/32/294589_2.png) [@sableraph](https://meta.discourse.org/u/sableraph)
#### Post date: [June 3, 2026, 12:26pm UTC](https://meta.discourse.org/t/inconsistent-meaning-of-yes-no-actions-in-the-review-queue/404418/1 "2026-06-03T12:26:08Z")

</div>

I love the new unified review queue but I noticed a slightly confusing UX pattern when processing a lot of items in a row.

You might review several flagged posts that ask “Is this post spam?” where clicking **Yes** means taking action against the post (with a confirmation). Then the next item asks “Approve this topic?” where clicking **Yes** does the opposite (without confirmation).

When you’re scrolling through the queue quickly, it’s easy to build up muscle memory and accidentally click **Yes** and approve a topic when you actually meant “Yes, this is spam.”

---

_[View the full topic](https://meta.discourse.org/t/inconsistent-meaning-of-yes-no-actions-in-the-review-queue/404418)._