The triggered job is parameterized, but the default values are not used

[jdjamsa1]

So if I use this plugin to trigger my job based on the content of some url, my job DOES get triggered but does not use the default parameter values that have been specified for it. Is that what you would expect?

[sdatko]

Hey,

I noticed this as well and for me this is definitely a bug. I explained why and described the steps to reproduce the bug, here: #37.

Yours,
Szymon

[TonyNoble]

This was due to an issue with xtrigger-lib, caused by the changes to parameterised jobs in Jenkins.

Resolved with release 0.50 of URLTrigger plugin