Iteration path of time-tracks of moved work-items

Hello @ all,

we have just installed 7pace for evaluation purposes. Now I have one question regarding the movement of work-items and the reporting of time-tracks of moved work items. Let's assume the following scenario:

You have a work items which is not doable within one sprint (I'm aware that that's something that should been avoided as it is against the principles of agile PM but in our case it can happen). That means that you start with the work item in sprint "A". You record time-tracks on it, etc.. By the end of the sprint/iteration you figure out that the task isn't finished and you move it to the next sprint/iteration (sprint "B") where you again track times. 

Now what we found was that the "iteration path" of each and every time track gets changed to the new iteration path when you move the work item to the new sprint/iteration (sprint "B") even though the tracks have been created in the sprint/iteration before (sprint "A"). That leads to the problem that  in the reporting of 7pace ("Time Explorer" and "Iterations") when you filter by iteration path, those entries are excluded. 

Now my question is if there is a possibility to avoid that 7pace overrides the iteration path of the already created time tracks when the work item gets moved? 

Thank you in advance for your support.

Best regards

Endre