Zephyr Enterprise: Losing link to requirement when test case associated to later releases

Hi. I am a very new user of Zephryr Enterprise...I am finding that the only way to make requirements (imported from JIRA in this case) available to map to a test case is to move those requirements into the Release-specific Test Repository folder relevant to that test case. You don't seem to be able to map requirements to test cases at the highest Project level. This isn't ideal but not insurmountable. But...the major pain IMHO then comes if, having mapped Test Case A to Requirement X and executed it during Release 1, you then want to re-execute Test Case A in Release 2  as a regression test. When you move Test Case A (by drag and drop) into the Release 2 Test Repository it seems to lose the link to the requirement (even though the Test Case ID is retained). In practice the mapped requirement for a particular test case will 99 times out of 100 remain the same throughout the project releases, so it seems quite an oversight to not allow the original requirement mapping to persist from one release to the next should the test case be executed in multiple releases. Currently, you would need to manually move Requirement X into the Release 2 area and re-map the test case to it again which is clunky. Or am I missing something ?? Any help much appreciated