cubicweb #1362090 single notification email on mass modification [open]
When publishing a version in the forge, you get 1 notification email for the state change of the version, plus one for each ticket whose state is changed. Same thing when several tickets are moved from one version to another in one go. I feel these cases should be better handled by the notification mechanism and a single mail should be sent. (submitting the ticket on the cw projet, but this might be tracket-specific) | |
| priority | normal |
|---|---|
| type | enhancement |
| done in | <not specified> |
| closed by | <not specified> |
similar entities
- cubicweb #1903304 [bfss] store the path to bfss storage independently of the file path itself
- cubicweb #901407 support for backup/restore of bfss
- cubicweb-forge #1399287 Change the standard validation process of the tickets
- cubicweb #1806898 ical view: UID is not unique across generations of the view
- cubicweb #3267833 move dataimport to a cube
[see all]
Comments
-
2011/02/09 17:09
add commentSimple way of doing this is to setup an operation in the hook rather than send the mail in the hook itself. The operation can gather all the notifications triggered in the transaction and sort them and group them correctly and send a single email to each person concerned.