Just some probably low-priority weirdness I ran into last night.
Expected Behavior:
Anyone who has permission to message a group (as defined on the group admin page) should be able to click on a link to generate a PM to that group.
Actual Behavior:
If someone with permission to message a group but not see it clicks a link to generate a PM, they get a box with the generic âSorry, an error has occurredâ message.
Note that this is specific to using a link to create the message - said user can still manually open up a PM, add the group to the PM, and send them the message without issue.
Repro:
Create a group with restricted visibility but that everyone is able to message
With a user that canât see but can message the group, click on a URL to generate a group message
âSorry, an error has occuredâ. Repro complete!
3a. No errors in /log or /sidekiq
When I submitted the bug report, this was actually an unintentional case - I was mostly concerned because it took some time to diagnose the issue and fix a short time event that was running. As well, it wasnât obvious that it shouldnât work, since you could still send PMs manually to these groups.
In general though, I think it could be useful if you wanted a group with private membership for some event or process to remain messageable, but maybe the others in this topic have a more specific use case in mind.
The use case for this scenario is where you want a group to be contactable but you donât necessarily want the membership of said group âadvertisedâ for some reason. Consider an âanonymousâ review panel for proposals or handling complaints, for example, where you donât necessarily want to disclose members out of concern of conflict of interest or undue influence.
There are surely other use cases, but thatâs the one that comes to my mind first.
