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

That was it, @Moin. Thanks! (No clue why that didn’t jump out at me from the list :roll_eyes:)

And what about thread update notifications? Does a ‘me too’ count as a reply for the purposes of getting reply notifications?

In a situation, where I’ve raised an incident based on a high ‘me too’ count, when I reply to the thread to ask users for additional details… who gets the notification?

1 Like

I’d say: it depends. The me too button changes the topic tracking status to “tracking”

The topic tracking status is also updated when you reply, but the notification level depends on what the user has configured in their preferences.


The default for that is configured by admins with the Default_other_notification_level_when_replying site setting, which is “tracking” by default.
So if the user preference is default, the button results in the same topic tracking as a reply. So if you reply to the topic instead of a specific post by default users who replied and those who used the button receive the same kind of notification: the topic will appear in the users unread/new list.
But I don’t think you receive direct notifications for replies in a topic you are tracking, so I am not sure if that is what you mean. For those who replied you can use an @here mention which is like notifying everyone who posted. This is probably something userss who used the new button would not be notified about.

1 Like

just a +1 for this, our support forum sees a lot of issues specific to an user that can’t possibly be the same as an issue experienced by a different user, in this case the “me too” button doesn’t make sense.

4 Likes

Totally fair — just to reiterate, in case anyone is unaware, this functionality is optional:

3 Likes

Does this feature include an admin report showing which topics have received “Me too” clicks, preferably sorted by count in descending order?

I am not requesting this for my own use, since I am not an admin on sites using the feature. However, I may be able to ask an admin to access the report. Without that access, I would not be able to provide feedback on the report as it currently exists—or on a new report if one is created.

Such a report might also be useful to general users. It could help them see which problems are being reported most frequently and determine whether they are experiencing the same issue.

1 Like

I like it, and I would agree it should bump the topic the first time a user pushes it.

I think “Me too” has a problematic connotation, but I also cant think of a better short text.

Used your question as a prompt directly in the data explorer UI to create one:

Prompt:

an admin report showing which topics have received “Me too” clicks, preferably sorted by count in descending order, filtered to open topics, with a params for date range when topic was last bumped

Query:

-- [params]
-- date :start_date = 2026-02-01
-- date :end_date = 2026-08-01

SELECT
  t.id AS topic_id,
  t.title,
  COUNT(si.id) AS me_too_count,
  t.bumped_at AS last_bumped_at
FROM discourse_solved_shared_issues si
JOIN topics t ON t.id = si.topic_id
JOIN categories c ON c.id = t.category_id
WHERE t.deleted_at IS NULL
  AND t.archetype = 'regular'
  AND t.closed IS FALSE
  AND t.archived IS FALSE
  AND t.visible IS TRUE
  AND c.read_restricted IS FALSE
  AND t.bumped_at >= CAST(:start_date AS date)
  AND t.bumped_at < CAST(:end_date AS date) + INTERVAL '1 day'
GROUP BY t.id, t.title, t.bumped_at
ORDER BY me_too_count DESC

And that can be added in the dashboard as well, if desired.


That said, I could imagine this being directly integrated into the “support” section of the new dashboard as well.

1 Like