Parameters passed to a downstream job are filtered out before being passed through to child builds. This effectively invalidates the parameterized trigger plugin.

Steps to reproduce:
1. create an upstream job which contains a property file
2. Create a downstream job which uses the contents of the property file
3. Have the upstream job trigger an instances of the downstream job for each property file found
4. The child job will trigger but not use the parameters from the plugin

Expected behaviour:
1. Updated documentation stating that the parameters MUST be declared in the downstream job
2. For the plugin in the upstream job to throw an error if the downstream job does not contain the appropriate parameters

Current work around is to disable the security fix as per instructions here https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170