Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Receiving/replying permissions (group threads) #3089

Open
2 tasks
ChrisvanChip opened this issue Sep 6, 2021 · 0 comments
Open
2 tasks

Receiving/replying permissions (group threads) #3089

ChrisvanChip opened this issue Sep 6, 2021 · 0 comments

Comments

@ChrisvanChip
Copy link

ChrisvanChip commented Sep 6, 2021

Is your feature request related to a problem? Please elaborate.

There's one thing left prior the new 'group-threads' being ideal for investigations: restricting users to speak (especially the ticket author).

• For investigations, I want to let someone explain their story without the other one interrupting.
• For reports, I want the reported one being able to tell their story without them knowing who reported them, nor letting the original reporter know what the reported one said. Using the Modmail thread is very ideal due to logging & centralizing the information.

Describe the solution you'd like

Since you can't remove the original ticket author (for obvious reasons), it would solve the issue to disable "receiving" and "replying" separately or both at once.

The commands could be (name is just an example):
?disableuser <ID> <receiving/replying/both>
?enableuser <ID> <receiving/replying/both>

Does your solution involve any of the following?

  • Logviewer
  • New config option

Describe alternatives you've considered

We are currently using multiple threads and constantly have to ping eachother and send message links, which is very inefficient. It works, but it takes a lot of time and wastes efficiency.

Who will this benefit?

• All moderators using Modmail (with group threads) for reports & investigations.
• All supporters using Modmail to let multiple affected users explain the problem in turns (so it doesn't clutter with multiple stories at once).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant