The Agile Gadget uses wrong end date when setting up a version to have a Master Version

The agile gadget extends the end date of the release to the date of the master release. This makes the Agile gadget unusable for iteration tracking.

1) What worked:
We had in project "X" versions:

• "0.1.0 Sprint 2" with start date 1 end date 7
• "0.1.0 Sprint 3" with start date 8 end date 15
• "2.0.0 Sprint 4" with start date 16 end date 23

When working in "Sprint 2", we set up an issue search filter:
project = X AND fixVersion = "0.1.0 Sprint 2" ORDER BY priority DESC

When displaying the Agile Gadget on the dashboard, we could use this filter, and the burndown would have an end date of date 7. This is as it is.

2) What did not work:
We discovered the "Master" version feature of Greenhopper, so we changed the version structure to be:

• "0.1.0" with end date 15
• "Sprint 2" with start date 1 and end date 7 having "0.1.0" as Master.
• "Sprint 3" with start date 8 and end date 15 having "0.1.0" as Master.
• "2.0.0"
• Sprint 4" with start date 16 and end date 23 having "2.0.0" as Master.

We changed the issue search filter to be:
project = X AND fixVersion = "Sprint 2" ORDER BY priority DESC
and also verified that we retrieved the same number and the same issues as in the working example above.

Now the problem is, that when we have the Agile Gadget configured to use the search filter for "Sprint 2", the graph is changed to have an end date of 15. This is an error.

I have included screenshots:
greenhopper-example-1.png is the working example.
greenhopper-example-2.png is the non-working example.