>>From: rdavis@... [mailto:rdavis@...]
>>
>> I was wondering if you might allow user-defined, custom
>> functions that
>> do custom processing when a bug is created or updated? In my
>> particular
>> case, I'd like to have the possibility to update some source
>> control job
>> management fields in another database (Perforce) when a bug
>> is created
>> or resolved.
>>
>> Adding the ability to add custom triggers would be
>> universally useful,
>> while also allowing me to easily port these triggers forward as the
>> codebase changed. I would only need to port my config file
>> and the file
>> containing the custom-defined triggers forward as the
>> codebase evolved.
>> The ADODB database abstraction layer has employed this mechanism with
>> great success.
>Such triggers would be really usefull! What I did with the custom field
>collections could also (and even more general) be implemented with such
>triggers.
We were working on Mantis roadmap earlier this week (or maybe last
week), and plug-ins were on the agenda. The concept of plug-ins is to
allow Mantis users to add their own code (or override standard code)
without having to change Mantis code. This is by implementing such
plug-ins (or what you call triggers).
For example, a user can implement a notification plug-in to send an SMS
rather than an email, or maybe have both. Or another plug-in to keep a
log of all actions done by a specific user (which pages visited,
...etc), and so on. For each of this plug-in types, there will be an
interface that the plug-in is expected to implement. Mantis will call
the plug-in methods with the appropriate parameters and it is up to the
user's implementation to do whatever actions needed.
Regards,
Victor.

From: rdavis@... [mailto:rdavis@...]
>
> I was wondering if you might allow user-defined, custom
> functions that
> do custom processing when a bug is created or updated? In my
> particular
> case, I'd like to have the possibility to update some source
> control job
> management fields in another database (Perforce) when a bug
> is created
> or resolved.
>
> Adding the ability to add custom triggers would be
> universally useful,
> while also allowing me to easily port these triggers forward as the
> codebase changed. I would only need to port my config file
> and the file
> containing the custom-defined triggers forward as the
> codebase evolved.
> The ADODB database abstraction layer has employed this mechanism with
> great success.
Such triggers would be really usefull! What I did with the custom field
collections could also (and even more general) be implemented with such
triggers.
CU,
Christian