Settings
Routing is about matching the right work.
| Control | Meaning |
|---|---|
| Off | No assignment or status-change emails. |
| Only errors assigned to me | Email when the user becomes the owner, and when one of their assigned groups changes status. |
| All matching workflow changes | Email for any matching assignment or status change in the project, even if the user is not the owner. |
| Environment match | Use all for every environment or choose one exact label, such as production. |
| Severity match | Use all for every severity or choose one exact level, such as error. |
| Status match | Use Unresolved for active work, Closed for fixed or ignored work, or All when both matter. |
Verify
Test with a real assignment.
- Make sure the recipient has project access and the workflow routing mode you expect.
- Assign an error group to the recipient.
- Change the group status as another user if you are testing assigned-to-me status mail.
- If no email arrives, check whether environment, severity, or status filters excluded the change.
Troubleshooting
Routing filters are exact matches.
| Symptom | What to check |
|---|---|
| No assignment email | The user may not have project access, routing may be off, or the mode may only send for assignments to that user. |
| Status-change email is missing | Status filters may exclude the new state, or the group may not match the configured environment or severity. |
| Too many workflow emails | Use Only errors assigned to me instead of All matching workflow changes, or narrow environment and severity filters. |
| Email arrives for another user | Each project member owns their own preferences; check the recipient's settings, not only the project owner settings. |