In group messages, the “Mark as Solution” button—provided by the discourse‑solved plugin—is no longer visible to users who previously had access to it. The button still appears correctly in topics:
This is a group message where we had used the button in the past and shows there’s a Solution, but the button to enable/disable is no longer there:
Is this a recent change or a bug, and is there any way to restore the button in group messages?
Are you saying it used to work for you in group personal messages? I have not seen that before and thought it was not possible, as per this other topic:
Interesting, based on that topic asking to offer the solved/unsolved filter in inboxes, I would expect the user was already using the solved plugin in inboxes. So I assume it worked when the feature was requested. Why do you conclude that it didn’t work at all?
Agreed. I don’t see how it can be enabled for group messages. Maybe that was a topic that was solved, and then converted to a message? What happens in that case?
Yes! depending on the version installed. Updating from 3.4.0.beta3-dev to 3.5.0.beta7-dev removes this feature
This is how it works on a group message on 3.4.0.beta3-dev:
Thanks!
There was a change in February: FIX: don't allow or count solutions in PMs by ZogStriP · Pull Request #334 · discourse/discourse-solved · GitHub
Pretty straightforward, this ensures we don’t allow users to mark a post as a solution in a PM.
This also ensures we don’t count solutions in topics that were converted to a PM.
Internal ref t/146766
Is that really intended? at least it should be available for group messages
I think this should be moved from Support to either Bug or Feature.
Since it worked until February and now no longer works, I’d choose Bug. But I don’t know what was discussed in the internal topic.
I’ve moved it to Feature as this change was intentional.
@Gerard_Cobas can you share more about your use case?
I do see two other related requests as well
I’ll do some topic merging in a bit, but in the meantime, continuing the discussion here is fine.
The second one is about adding the solved/unsolved filter, which of course requires the solved plugin in group inboxes. But it’s a different request.
Hi Dave, thanks for picking this up!
A bit of context on our side: we use group private messages as shared inboxes for support, following a pattern similar to what’s described here: Use Discourse as a private support ticket system
Our support agents rely on the “Mark as Solution” button to indicate when an issue has been resolved. This serves two purposes:
/admin/api/web_hooks/38/edit) that fires when a post is marked as a solution, syncing with our backend system.Group PMs are core to our support workflow, and we handle a significant number of account-specific topics, which makes public topics unsuitable.
The solution marker is more than just a UI element. It is part of our internal process, and without it, agents can’t properly close tickets or trigger the automation that depends on it.
Even though it’s a small change on the surface, it breaks a critical part of our workflow, so we’d really appreciate a reconsideration or an alternate approach.
Thanks!
I decided to keep those two topics open and retitle them as they are both more specific requests, although they both depend on this one.
Thanks for the extra context, Gerard.
Allowing solutions on group messages feels like a bit of an accidental feature, but I understand better why you were relying upon it now, and I see evidence that others were doing the same in those linked features.
Given that, I’m thinking it may make sense to make it more explicit to enable this feature in the solved plugin with a new like allow_solved_on_group_messages (bool, default disabled) or allow_solved_in_groups (group list, default empty).
The latter would also address Enable solved plugin for specific groups inboxes
I’ll see what others think about these options or other alternatives.
