bug report when pasting transition

When I'm working in the timeline (FCPX) and I have a transition I've made (example - Slide In / duration 4 frames) and I create a second transition by using the Command T shortcut to place a default dissolve, and then I copy the transition I already made and paste it over the default dissolve, everything works perfectly, and the default transition inherits the attributes of the copied transition, (so it becomes a Slide In with a 4 frame duration), but the playhead jumps to the beginning of the timeline.

Usually when I working like that I'm magnified at least to the point where I cannot see the beginning of the timeline if I'm down the piece a ways, so after pasting the transition, and after the playhead leaps to the beginning of the timeline, I thn have to SHIFT Z (to see the whole timeline), find where I was, place my playhead bck where I was working, and then Command + to magnify that area so I can continue working.

As always, I'm in a hurry with hard deadlines, and I am writing to your forum to see if any of you know what I'm talking about or if this issue is only a bug on my system. I have to be honest and admit that I've had some great experiences here and some unusual ones. I've been editing in FCP way back from when Apple first bought the software from Macromedia and like some of you, I went through FCP3 up to 7 and eventually tried X as well as Premiere and a short bit with Media Composer. Both Premiere and MC are very good and absolutely pofessional, but I missed FCP and I came back to it and I continue to edit on it and I enjoy the speed and miss a few things but overall X seems good enough for me and it gets better with every update.

I'd have to admit I'm probably pretty old compared to a lot here on the forum, and sometimes it's odd when I get a sudden reply that is sort of at a elementary level, stating the obvious, or worse, completely useless. I am most fond of the calm and thorough advice and direction I have received from Tom Wolsky, of course, and many others, but I just want to say that I only post when I'm certain of an issue, and I'm very thorough as well. I'm not saying I'm great, I'm saying I'm experienced.

I've given this particular bug to Apple through the feedback avenue in FCPX. Please if you are not up to your necks in work (like I am) let me know if you're familiar with the bug or if it is not happening on your system.

Thanks - Stephen