I think we've got just the thing, Tom - $listAll or $repeatAll.
You're right, when reporting in the context of a requirement, you'll normally get the issues that apply only to that requirement, unless you use one of those $All keywords. Since you can also report on issues at the top level, these keywords allow you to perform a list (or repeat) for EVERY issue in the project, regardless of the owner.
All sorting and filtering syntax used by their base forms call also be used with the "All" variations; you'll probably want to do some filtering and maybe even set up a variable or two to prevent a whole bunch of duplicate listings in your report.
As a side note, where clauses can actually use variables, too. Just make sure you're using the double dollar sign ($$). Let's say for example you want to set up a variable on each requirement so that you can match your custom field later to your issues' resolved date. I'll call my custom field "CustomDateField."
$repeatRequirements where Type = Document Revision
$set $$datecheck $CustomDateField
Now that we've got the variable set, you can show the issues that match that using a 'where':
$listAllIssues where DateResolved = $$datecheck $Description
So, the above will list all of the issues from your entire project with a DateResolved property that matches the current requirement’s CustomDateFIeld value.