We have some jobs that use this plugin to launch a child job execution. A major usability headache is that you can't directly find the child execution from the parent. A link is printed to the parent job at the start, and to the specific execution once it completes, but if you look at a life job, you have to go scrounging through lists of running jobs to find the child job. E.g. if you look at this log output, the job ID is only printed several hours after the job actual starts.
I started working on a potential patch for this - https://github.com/timarmstrong/parameterized-trigger-plugin
I haven't worked on Jenkins code at all so would welcome feedback on whether this makes any sense and whether I'm heading in an appropriate direction.