The "All Changes" view is always blank for the case below:

We have several build jobs for each of our branches of development each with their own set of changes. All of these build jobs trigger the same test job with a parameter specifying the branch it is from. There are unique artifact fingerprints in each build job run that is also fingerprinted in the test job.
The Build History for the test job could look something like this:
TestJob_Branch_A
TestJob_Branch_C
TestJob_Branch_B
TestJob_Branch_C
TestJob_Branch_A

In other words the test job runs are triggered from different jobs are not grouped by the origin job.