comparison doc/customizing.txt @ 684:5b23ff865f3a

added a "detectors" directory... ...for people to put their useful auditors and reactors in. Note - the roundupdb.IssueClass.sendmessage method has been split and renamed "nosymessage" specifically for things like the nosy reactor, and "send_message" which just sends the message. The initial detector is one that we'll be using here at ekit - it bounces new issue messages to a team address.
author Richard Jones <richard@users.sourceforge.net>
date Mon, 08 Apr 2002 03:40:31 +0000
parents 604c84696461
children c52122f38c9b
comparison
equal deleted inserted replaced
679:5a4dd342d827 684:5b23ff865f3a
239 create(information) 239 create(information)
240 ::::::::::::::::::: 240 :::::::::::::::::::
241 241
242 Create a node in the database. This is generally used to create nodes in the 242 Create a node in the database. This is generally used to create nodes in the
243 "definitional" classes like "priority" and "status". 243 "definitional" classes like "priority" and "status".
244
245
246 Detectors - adding behaviour to your tracker
247 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
248
249 Sample additional detectors that have been found useful will appear in the
250 ``detectors`` directory of the Roundup distribution:
251
252 newissuecopy.py
253 This detector sends an email to a team address whenever a new issue is
254 created. The address is hard-coded into the detector, so edit it before you
255 use it (look for the text 'team@team.host') or you'll get email errors!
256
244 257
245 Web Interface 258 Web Interface
246 ------------- 259 -------------
247 260
248 The web interface works behind the cgi-bin/roundup.cgi or roundup-server 261 The web interface works behind the cgi-bin/roundup.cgi or roundup-server

Roundup Issue Tracker: http://roundup-tracker.org/