그룹 메시지에서는 “해결로 표시” 버튼(discourse-solved 플러그인 제공)이 이전에 해당 버튼에 접근할 수 있었던 사용자들에게 더 이상 표시되지 않습니다. 토픽에서는 버튼이 여전히 올바르게 표시됩니다:
이것은 과거에 해당 버튼을 사용했던 그룹 메시지이며, 해결이 표시되어 있지만 활성화/비활성화 버튼을 더 이상 찾을 수 없습니다:
이것은 최근 변경 사항인지, 아니면 버그인가요? 그리고 그룹 메시지에서 버튼을 복원할 방법이 있을까요?
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!
1개의 좋아요
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
1개의 좋아요
Is that really intended? at least it should be available for group messages
1개의 좋아요
이건 #support에서 Contribute > Bug 또는 Contribute > Feature 중 하나로 옮기는 게 좋을 것 같아요.
2월까지 작동하다가 이제 안 되니까 #contribute:bug를 선택하겠습니다. 하지만 내부 토픽에서 어떤 논의가 있었는지는 모르겠어요.
2개의 좋아요
이 변경은 의도된 것이므로 Contribute > Feature 채널로 옮겼습니다.
@Gerard_Cobas 사용 사례에 대해 더 자세히 알려줄 수 있을까요?
2개의 좋아요
I do see two other related requests as well
- Enable solved plugin for specific groups inboxes
- Ability to filter solved / unsolved messages in group PM inbox
I’ll do some topic merging in a bit, but in the meantime, continuing the discussion here is fine.
2개의 좋아요
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.
1개의 좋아요
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:
- Internally, it helps the team quickly identify and close resolved conversations.
- Programmatically, it acts as a trigger. We have a webhook set up (e.g.,
/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!
2개의 좋아요
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.
1개의 좋아요
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.
7개의 좋아요
It could also be a setting in the group configuration.
Then you can enable it in the place where you enable the group inbox. The Assign plugin also adds a setting there:
3개의 좋아요
그렇다면 이 부분에 대해 어떤 진전이 있었나요? 이것이 왜 무조건적으로 제거되었을 수 있는지 이해할 수 없습니다. solved 플러그인을 개인 그룹 메시지에서 사용하는 사람들이 정말 많습니다.
3개의 좋아요
이 문제는 우리에게 매우 큰 영향을 미쳤습니다. 내부 지원 시스템은 Discourse API의 “Solved” 플래기에 의존하고 있습니다. 이를 다시 활성화할 수 있는 우회 방법을 권장해 주세요.
3개의 좋아요
우와, 플러그인을 업데이트했는데 헬프데스크에서 해결됨 버튼이 사라진 걸 알아차렸어요… discourse 팀 자체도 헬프데스크로 사용했기 때문에, discourse를 헬프데스크로 사용하라고 제안했을 때 그걸 따랐거든요. 이 용도가 더 이상 유효하지 않나요? 기능이 점점 사라지고 있고, 초점도 잃어가고 있는 것 같아서요.
1개의 좋아요
이 문제에 대한 업데이트가 있나요? 업그레이드 시 solved 버튼의 기능을 유지해야 합니다. 이 기능이 없다면 업그레이드를 진행할 수 없습니다.
1개의 좋아요
좋은 소식 @here, 다시 돌아옵니다 
8개의 좋아요