I'm using the email-ext plugin and it works great except for this problem with "showDependencies".

This is how I use it (I only use global configs for all jobs in email-ext, just triggers are set per job):
${CHANGES, showPaths=true, showDependencies=true}

I have a 'build' project A that triggers 'unit test' project B, C and D. B, C and D are shown as "Downstream Projects" on project A's "Status" page.

B and C are started by standard "Build other projects" post-build action of A.
D is started by "Build other projects (extended)" post-build action of A if Build result is "Equal or over SUCCESS" and with "Trigger only if downstream project has SCM changes" - that is available due to https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin, version 2.21.

When project B fails due to a change in project A's SCM, in the email I don't see the commits from project A that resulted in this failure, although "showDependencies" is true.

Did I misunderstand what "showDependencies" is meant for or misused it? If that's not its purpose, then please consider this a feature req. to add the ability to have the changes from A above in email.

Thanks.

BTW: from token docs, it seems to me that you can't use "showDependencies" with ${CHANGES_SINCE_LAST_SUCCESS}, just with ${CHANGES}. Is that true? Cause that would be exactly what I want.