P4DTI issue job000155

TitleBugzilla integration doesn't send mail when bugs change through P4DTI
Assigned userNick Barnes
DescriptionBugzilla sends email notifications when bugs change through normal Bugzilla use. But when bugs change through the P4DTI no notification is sent.
Bugzilla has a Perl script called "processmail", which it runs whenever a bug changes. It analyses the bug activity and may send mail to one or more Bugzilla users describing that activity. We don't do this, or emulate it, so Bugzilla bugs will be changed by the replicator without email being sent out.
AnalysisWe could support this by invoking processmail ourselves. We would have to (a) add code to compute parameters for processmail and invoke it, and (b) add a replicator configuration parameter which locates processmail. Users who want to run the replicator on a different machine from the Bugzilla server can still do that, by copying the processmail script.
How foundinspection
EvidenceI just know.
Observed in0.5.0
Introduced in0.5.0
Created byNick Barnes
Created on2000-12-13 13:30:33
Last modified byGareth Rees
Last modified on2001-12-10 19:14:17
History2000-12-13 NB Created.
2001-01-16 RB Set priority to "essential".


Change Effect Date User Description
7787 closed 2001-01-29 14:57:09 Nick Barnes change history.
7786 closed 2001-01-29 14:55:04 Nick Barnes doc for bugzilla_directory variable.
7676 closed 2001-01-26 15:54:25 Nick Barnes processmail wasn't working because I had the SQL tables locked. Should be OK now.
7637 closed 2001-01-25 15:30:51 Nick Barnes processmail. This is the first cut at simulating the Bugzilla logic (from process_bug.cgi).
7634 closed 2001-01-25 13:25:58 Nick Barnes First hack at processmail.