It would be great to automatically generate "transitive" release notes - i.e. release notes including other release notes by aggregation.

Use cases:
1) in our appX, we're changing version of depX from 1.9 to 1.10 and we need to "publish" new depX-1.10's features as if they were appX's
2) in the upcoming version of our appX, we're reintegrating code from different projects (prjX, prjZ, etc.), and we need to merge their release notes
3) in bugfix release 3.0.4 we're only porting fixes of the older 2.2.9, so 3.0.4 is basically a one-issue-fixVersion with an almost-empty release note instead of the real, informative, one

In all cases we have:

• a transitive release note that we'd like to include/merge in the final one
• one or more issues (Tasks) representing the activity of updating/reintegrating/porting; these issues usually identify cleary and precisely the unique Project+FixVersion being somehow "included"
• the actual release note being non-informative

Would it be possible, while generating the release note, to replace these special/transitive issue with the referenced releaseNote?