Allow to mute users
Open, LowPublic
Actions

Assigned To

None

Authored By

	valerio.bozzolan
	May 2 2023, 11:37

Description

Premising there are many wrong reasons for muting a person,

There are several legitimate reasons for muting a person. One of them is this use case:

I have an account foo.yeah used for volunteer reasons, but also an account name.surname.nice-organization-name used during working hours activities.
- Ideally, the user foo.yeah should be able to mute name.surname.nice-organization-name to avoid to receive self-actions during working time
- Ideally, the user name.surname.nice-organization-name should be able to mute foo.yeah, to avoid to receive self-actions during volunteers time

A way to implement this is:

Introduce an option Muted Users in the Config page somewhere
Modify the current Mail and Notification system to skip that notification if it comes from a Muted user

valerio.bozzolan triaged this task as Low priority.

valerio.bozzolan created this object in space S1 Public.

avivey renamed this task from Allow to mutate users to Allow to mute users.May 2 2023, 13:52

avivey updated the task description. (Show Details)

I think you can get there using herald:

"Notification" is the "not email" - I think there's no way to not have a notification at all.

Maybe it should be extended to "ignore event".

Also, the herald rules for "mail" is a bit of a mystery to me.

Do you remember what the "Do nothing" Herald rule is about?

"Do nothing" does nothing. It's mostly for working with the "Other Herald Rule" conditions.