Solved improvements: Allowing members to indicate they’re experiencing a reported issue

When a member finds an unsolved topic that describes an issue they’re also facing, there’s been no easy way for them to signal that or get updates about solutions to the topic. To address this, we’ve added a Me too button to unsolved topics in support categories, which members can click to indicate that they’re impacted by the reported problem and opt-in to receive a notification about the solution.

In this topic, we’ll review the major changes and share how you can start using this today.

What’s changed

An unsolved topic in a support category now shows a Me too button in the first post. Members can click it to indicate they’re experiencing the same issue.

Members can click the "Me too" button on unsolved topics to share that they're impacted by the issue and receive a notification when the topic is solved.1332×482 22.1 KB

When a member clicks Me too, a few things happen:

• The counter within the button ticks up. The counter always starts at 1 to represent the topic author.
• The topic tracking will be set to Tracking, which means they’ll receive a notification when the topic is solved.

If a user that’s not logged in (i.e. an anonymous visitor) clicks Me too, they’ll be prompted to log in or create an account. The Me too button disappears once a topic is solved.

Turning on the “Me too” button in your community

For now, this is considered an experimental change! We’re welcoming your feedback, which will help us make improvements and roll this out further.

To turn this on, head to the Upcoming changes page in your admin area (/admin/config/upcoming-changes) and find the Enable solved shared issues item. Update the Enabled for… field to opt your site in to this new design:

You must also turn on the Enable support type category setup upcoming change to use this feature.

The "Enable solved shared issues" upcoming change item, which you can enable to add the "Me too" button to unsolved topics.967×258 27.3 KB

What do you think?

We’re eager to hear how this is working in your community — please share your feedback here and let us know how we can continue to improve support categories for you and your members.

This is neat!

I’d be interested in seeing an option (or perhaps with Data explorer) to be notified as an Admin if X amount of people choose “Me too”.

This seems like a strong way to signal high pain points - and ideal for marking the solution, providing one, or escalating internally for us. Seems especially useful for prior conversations from months ago that I’m not regularly reading now, but people may still be experiencing issues with

Is it possible for such topics to be bumped when a Me too is clicked? Otherwise topics from years ago could get high counts, but with little visible effect. (Perhaps behind a setting to not create noise for some communities)

Right now, this feature is more focused on the member side (making it easy for members to opt-in to notifications about the topic’s solution), but there are definitely ways we can make it more useful to admins/staff, as well, like reporting on the “Me too” counts or helping those surface in other ways.

Keep the ideas coming!

Do you have a designated test topic to see this? Not sure if it’s cool to create one in Support just for this.

This may be the nudge that has me convert my existing question/support categories to the “support” type.

This feature is not enabled on Meta.

Let me enable it on https://try.discourse.org/

EDIT

It’s enabled in https://try.discourse.org/c/support/50

just tried it, it’s working

Thanks!

While I was setting it up, the power went out in the whole neighborhood and the internet connection went down. Try again now.

Is this the same as a “boost” with the words “Me too”, or something else?

(P.S. Just checked and it seems to be different.)

It’s completely independent from the boost feature (which is still experimental). By clicking “me too” you opt in to receive a notification when there’s a solution selected. If you used a boost to do that instead, you would not be notified when the topic is solved.

Not finding this on my forum have all needed things enabled

Have you looked under Admin > Upcoming Changes? For the TWA forum, this is what I see:

image1448×396 35.4 KB

So it hasn’t been enabled yet.

I think the “Me too” idea is great.

This is something that has been needed for years. That said, the way I would ideally like to see it implemented may not dovetail with how I understand the current design.

My understanding is that this feature is scoped to the world of Discourse topics. On the OpenAI forum, for example, there is often a broader need for a “Me too” signal when users are affected by outages or service issues, such as OpenAI servers being down, a specific API endpoint not responding, or a Codex regression affecting multiple users.

However, those cases are often tied to systems outside Discourse, such as:

• OpenAI Status
• Codex Issues

From what I understand, this update does not interact with those external systems. It helps members indicate that they are experiencing the same issue in a Discourse topic and opt in to receive a notification when that topic is solved, but it does not appear to connect that signal to an external status page, GitHub issue, or incident tracker.

A recent OpenAI forum example is this topic:

https://community.openai.com/t/realtime-api-sip-inbound-calls-failing-again-before-webhook-dispatch/1380763

That topic collected multiple user reports and was later linked to this OpenAI Status incident:

https://status.openai.com/incidents/01KRG0AZKH41DV4D9SNJSXM33Q

So, is my understanding correct that the current “Me too” feature is limited to Discourse topics themselves, and does not currently provide a way to connect or synchronize that signal with external systems such as status pages or GitHub issues?

For real-time issues that attract many “Me Too” replies, users often begin reporting that the issue is resolved before it is officially confirmed solved, sometimes even an hour or more earlier.

It might be useful to have a companion option such as “Works for me now” or “Resolved for me” that is also tracked and signaled.

The idea would be that “Me Too” helps show how many users are affected, while “Works for me now” helps show when the issue may be clearing up in practice.

Here is a real world example of this:

https://community.openai.com/t/my-custom-app-connectors-have-disapeard/1381144/10

I had just updated the forum after posting here but i did look there let me check again

cause when i searched for it i did not find it

Ok now i see it and was able to enable it thank you nate

Nice idea, I like it!

Two things

No. It says “me too”. It should start at no counter ie. 0.

Additionally, it would be nice to be able to see who clicked “me too” in a topic.

The counter represents how many people are impacted by the issue, so it starts at one to reflect the topic author.

I think I’m with @RGJ on this one. Having seen it in action on this topic, I thought “wow, kinda interesting to see someone else experiencing this seemingly niche issue” to then realise it was still just the OP.

“too” is additional. It implies additional to the OP, not inclusive of

In that case the button should be called “I have this issue”.
But “too” indicates additional users.

I really like this idea! I’ve been seeing it on Meta and was fairly confused when I noticed every topic had at least one and thought that somebody must have gone down the list and voted for everything but I learned that wasn’t the case when I went to the sandbox, made a topic, and noticed I had automatically voted for it.

It seems weird to me that the “me too” button is automatically selected for the reporter. I’m not sure how other platforms implement it but I would have figured it’s more similar to liking where you can’t select it on your own posts. Obviously this is a nonissue but I’m just a little confused as to why I’m automatically saying “me too” to my own problems.

Edit: oops.. this was a discussion already, should have scrolled down a little more. I’ll leave this up though because what I said still stands

Thanks for the feedback everyone, we’re removing OP from the count here:

@awesomerobot - I see that there is a site text for 'Me too (%{count}), can ‘Me too’ be updated to whatever we may see fit based on community?

Is there any impact if the site text is updated to reflect desired text?

Looks to work just as you’d expect:

image250×126 6.53 KB

image503×229 33 KB

yes you can change it, there shouldn’t be any problems

Should the “me too” button appear in a deleted, closed topic?

If you’re asking the group, my answer would be: make it a customization option.

I can see why some communities would want to allow this. However, in my experience, preventing users from updating closed topics often encourages them to look for an existing active topic or start a new one instead.

Another option would be to preserve the “Me Too” signal even when the topic is closed. For example, if a user clicks “Me Too” on a closed topic, they could be offered a simple option to open a new topic, after AI first checks whether there is already an active topic covering the same issue.

This is indeed a good design, but I still hope it can be used as a configurable option for Categories. For example, I have a category used for both brainstorming and progress tracking. It uses Topic voting to count how many people support something, and it also uses Solved to serve as a solution when a test version is available, after which everyone moves to another topic for testing and improvement. Currently, due to this feature, the category displays both Topic voting and “Me too,” which actually causes some confusion. In fact, I use Solved in many scenarios, but I only want to use “Me too” for a category that serves the function of Bug feedback.