Sure, at our organization, we create a Test Plan document, have it reviewed, approved, and released in a separate doc control system before beginning to execute the tests it contains. At the end of test execution, the Test Results must also be approved and released in our doc control system as well. The tests in each must match, or at least, the changes must be clear. If we were executing tests the old way, on paper, we would record test results on a printed copy of that approved version of Test Plan. It would be clear that we were executing the same version of tests that were reviewed and approved. There is now concern about losing that link when moving to electronic results capture within Jama.
Executing tests electronically within Jama means you have to create a separate export/document for your Test Results once you're done testing. This document is generated from Test Run items, rather than the Test Case items that the Test Plan document is generated from. The link between the two is in the Test Case tab of the Test Run items. If that information can't be exported to the document, then correlation between the two documents becomes much less clear.
Our documents must be able to stand on their own outside of the Jama tool. Without some way to show the version of each test case in the Test Plan vs. the version of each test case executed in the Test Results, the only way for an auditor to ensure a match is to compare every step of every test case.