Some or One?

Do they have "Send me an email" Herald actions? Herald is now stronger than notification preferences, after T7731.

You should be able to use bin/mail list-outbound + bin/mail show-outbound --id <id> to confirm this. T5791 will eventually build a self-serve web UI so users can learn these rules more easily.

If this is the cause, the Herald rule can likely be adjusted by adding a condition like:

[author][is not][alincoln]

I've only confirmed one so far.

This is getting me know. I have self actions off but to email me when a new task comes in. The Herald rule now overpowers the setting.

Can you add a condition like:

[ Author ][ is not ] [ @chad ]

...to your rule?

I promise I'll learn how to use the product before I ask for a salary.

We should definitely write a "useful things you can do with Herald" or "Herald Recipe Book" document at some point, there's a bunch of stuff that isn't very obvious until you know what the answer is.

T7826 was a recent similar case where Herald is powerful enough to express something, it just isn't obvious how to build a ruleset.

So I think Herald rules are the culprit on our end, but I can't figure out how to fix it:

Rule Description

When all of these conditions are met:
Projects include any of Platform Hardware

Take these actions every time this rule matches:
Send an email to squad-platform

There is no 'author usually does not like getting email for self actions' conditions.

"Object" and "Global" rules don't punch through settings, so that rule shouldn't be the culprit unless I screwed something up with the implementation.

The problematic rule would be a "Personal" rule owned by the user reporting the issue, which takes a "Send me an email" action.

(After T5791, there will be a link you can click to immediately identify the rule.)

@cburroughs

These aren't quite the same. One is a new condition/field, which would let you write rules like this ("mail me about all zebra stuff, except if I took the action"):

If: 
[ Description ] [ contains ] [ "zebra" ]
[ Acting user ] [ is not ] [ chad ]
Take action:
[ Send an email to ] [ chad ]

One is a new action, which I assume is for writing rules like this (":

If:
[ Projects ][ do not include ][ X, Y, Z ]
Take action:
[ Add project ][ you-forgot-to-add-a-mandatory-project-you-must-add-x-y-or-z ]
[ Assign task to original author ]

If this is the intent, a better implementation might be "assign task to acting user", but regardless it's an action for Maniphest tasks rather than a condition for all transaction-edited objects, so it's not quite the same.