You're reading one of the top pains on Discourse Meta — a free sample of the catalog. Create a free account to browse all Shopify & Atlassian pains and the basic Chrome catalog.
Discourse forum admins lose at-a-glance unread topic count after UI update
.54
Demand — how loud & how many (score)
Willing to payNo signal
Momentum (7d)▼ 2%
Cluster6 posts · 5 people
MarketplaceDiscourse Meta
Updated19d ago
The story
The pain
We rely on the unread count on the main page to quickly see if tracked topics have new activity. The recent update removed this, forcing us into extra clicks and hiding critical information. Our users are complaining, and we need a way to restore the old behavior.
Evidence
What people said · 6 complaints, 5 people
There is no easy one-click way to view tracked topics now, you have to do it with 2 clicks, and you can’t see the info at a glance. It’s not gone down well. I’d like a way to reverse it.
Ok, I still find that a bad idea to lose such information from main page My 2 cents after thinking about it for a day or so : If it was really the wording that was confusing, you should just have renamed “Unread” as “Tracked” or something like that, I know I’m late in the discussion, but now I got that on my instance, I’ll see what I can do to get it back this important data with theme or component)
not having the “unread” count on the main page is a big loss for me (and some of my users complained too). First thing I want to know when I get on the forum is to see if the topics I’m tracking had activity, having it mixed with the “new” count is not really logic in my point of view, they are not the same things.
Export the pain — problem, evidence and market signals — as Markdown, PDF or JSON. The Markdown export ships with a built-in briefing you can hand straight to a developer or an AI agent.