Ticket #112 (closed fixme: wontfix)
trac sends all mails twice to lumiera-work
| Reported by: | ct | Owned by: | |
|---|---|---|---|
| Priority: | nice | Milestone: | |
| Component: | infrastructure | Keywords: | trac python |
| Cc: | Blocked By: | ||
| Blocking: |
Description (last modified by ichthyo) (diff)
The default behaviour of Trac seems a bit annoying in this case. We have the CC to lumiera-work, thus, when a reporter also is registered to lumiera-work, (s)he sees each notifications twice. Does anyone know if this can be configured better?
Change History
comment:2 Changed 3 years ago by ct
- Status changed from closed to reopened
- Resolution done deleted
aah, i think this was wrong, it sends it to lumiera-work and to the user who did the edit. Anyone has a idea how to archive emails to lumiera-work (cc'ed there) and not send to the user reporting stuff (configureable) while still have his email registered in trac?
comment:4 Changed 2 years ago by ichthyo
- Priority changed from normal to lesser
ah, just stumbled across this one.
I am in doubt these duplicate mails are really a problem -- not every reporter reads lumiera-work.
This behaviour can be configured in the trac.ini, in section "notifications". You can define there the reporter, the owner and/or the changer of tickets to receive mails. By default, the reporter is enabled here, which is sensible IMHO.
Personally, I've configured my mail client with a filter to collect the lumiera-work items immediately. Thus, I just get the notifications on tickets created by myself into my inbox, which looks convenient for me.
comment:5 Changed 2 years ago by ichthyo
- Priority changed from lesser to nice
- Description modified (diff)
It seems that, based on the default configuration options in trac.ini, not much can be done here. If we remove the always_notify_updater setting, then a reporter not reading lumiera-work won't get any notifications.
It would be desirable to have a default, which can be adjusted by each user individually in his/her profile.
But currently we rather don't have the time to investigate this further. Anyone?
look ok now, anyone gets this twice? I close it