Adding a story to Version should automatically update its sub-tasks

In JIRA, the sub-task that is created after the story has fixVersion will get all the sub-tasks to be part of the same fixVersion. In GreenHopper Classic Board, adding the story to a version will get all its sub-tasks to be updated to the same version as well. This does not apply on the latest JIRA Agile.

It would be good to have the sub-tasks to automatically be added or prompt the user whether to add to the particular version, when the story (its parent) is added to the version. This is known to be a useful feature in Classic board, and lacking of this feature could affect the metrics such in the following scenario (given by customer)

• I did not manage to complete the story before end of the version, so I have to move it. The Story will be listed under the new version but the actual work is still in the old version.
• In the version workload report, I cannot see the sub-task efforts in the correct version, so I am mis-lead and will think, I can still add more to the new version, but the workload should already be 100% if the tasks had followed the story.
• In the agile rapid board, the versions list the remaining efforts, but the remaining effort is incorrect because the sub-tasks are in the wrong version.
• In the progress reports (agile and non-agile), the wrongly versioned sub-tasks will show up as an added effort, added too late in the process.