Does the logic of the Advanced Release Burndown report require me to keep marking the current iteration as we proceed forward in a release?

I have an iteration structure (actually one of many in my timeline) with a release-level iteration and the required project release plan for that iteration along with 10 sprint-level iterations beneath. The start date of the release-level iteration matches the start date of the 1st sprint-level iteration and the end date of the release-level iteration matches the end date of the 10th sprint-level iteration. This is supposed to define the scope of the release. Note that none of the sprint-level iterations overlap, but there are gaps between them (which should be OK).

The problem I have is that when none of the iterations are marked current, the report generates "stacked bars" for each iteration out through the end of the release, instead of stopping with the most recently completed sprint-level iteration and then drawing the three projection lines (optimistic, best guess, pessimistic). The remaining and velocity points are correct with respect to completed sprint-level iterations, but then they flatten out (showing no progress) through the end of the release. The ideal line is there as normal.

I guess I expected the report to key off of the sprint-level iteration start and end dates, not the fact that an iteration is marked current. I don't believe it is wrong to assume an iteration is complete when it's end date has passed.

Perhaps this can be an option of the report??

Now, assuming I do need to mark the current iteration as current, and I have done that (and waited a day), I still don't get the proper report. The report data still shows it does not know the current iteration, nor does it know the end date for the release even though it knows the end iteration.

How do I go about figuring out what is wrong here??