incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <>
Subject Re: [Apache Bloodhound] #210: Cleverer ticket CC behaviour
Date Wed, 26 Sep 2012 01:10:05 GMT
#210: Cleverer ticket CC behaviour
  Reporter:  mbooth       |      Owner:  nobody
      Type:  enhancement  |     Status:  new
  Priority:  major        |  Milestone:
 Component:  trac core    |    Version:  1.0
Resolution:               |   Keywords:

Comment (by olemis):

 Replying to [comment:1 mbooth]:
 > When I make a change to a ticket I don't want to be emailed about that
 change (I was there!) I only ever want to know when a change was made to a
 ticket by someone else.

 That depends on how you configure Trac notifications . For instance , if
 you changes are always Cc-ed to a mailing list you are subscribed , well
 ... I don't know how to stop delivery of such message . Use of email2trac
 is another case to consider as [#comment:2 mentioned before] .

 Finally I notice there are configuration options involved . Listed
 [#notifyselfcfg below] . This makes me wonder whether the scope of this
 ticket is limited to ASF issue tracker (i.e. this site) and therefore , if
 this is the case, I'd suggest to set ''component'' =
 [query:?status=!closed&component=siteadmin siteadmin] instead . Otherwise
 I guess we'll need more details about the characteristics of the specific
 deployment environment , or further clarification .

 ==== Related notification config options #notifyselfcfg

 [[TracIni(notification, always_notify_owner)]]

 [[TracIni(notification, always_notify_reporter)]]

 [[TracIni(notification, always_notify_updater)]]

 [[TracIni(notification, smtp_always_bcc)]]

 [[TracIni(notification, smtp_always_cc)]]

Ticket URL: <>
Apache Bloodhound <>
The Apache Bloodhound (incubating) issue tracker

View raw message