I'll see what I can do. I've had to hack this area around a bit already.
The revision matching stuff is tricky because Hudson can't easily tell if the build is using a custom implementation of ivy revision matchers, custom latest strategies, etc.
Perhaps the best would be to allow the user to enter a regular expression for matching revisions to be linked up as build triggers. If it's left blank, the behaviour will be identical to what it is now, otherwise the user-provided regex will override the default behaviour.
Oh, and is this when using Freestyle jobs with the Ivy Build Trigger or using the new Ivy Project functionality added in version 1.0 of the plugin?
added the component