How to manage documents in Jama?

Hi Omer,

we are a medical device company and we use the explorer tree only to create and collect the test cases, but the Test Plan area for writing test plans and executing the tests and we have our own velocity report templates for both, test plan and test report.

The test plan template basically exports the content of the test plan overview and all the test cases grouped by the test groups, but without any results. The test report template then exports the test plan overview and all the test runs, grouped by test cycle.

In the Test Plan area, we create separate Jama test plans for a "test plan" and a "test report". A "test plan" test plan is not executed and it only contains the test groups with the test cases. It is only used to create and export the test plan document for approval. A "test report" test plan then contains the exact same test cases and test groups, but including the test cycles and executed test runs with the results. In our case, the overview section for a "test plan" test plan is different to what is in the overview section for a "test report" test plan with results. Therefore, we have also created two different editor templates for that. Depending on the type of test plan, we select the respective template before filling out the respective content in the test plan overview.

Regards

We don't have an appendixes section in our test plan. We basically just have a table referring to any external documents.

But you could add a separate rich text field "Appendixes" to the test plan item type and create a velocity report template, which exports the content of this field after all the test cases.

For creating our velocity report templates, I used the following community reports from Jama as base and modified it to fit our own corporate document template and to also have our custom fields inside:
Test Plan Report
Test Results Report - Grouped by Test Cycle

Hi Jacob,

we have a signature table included in the Editor Template and we simply print the report and collect the signatures with respective date of approval.

Per,
our processes are still very "analog" in this case and might not be considered as best practice. We don't pay attention to the approval workflow within Jama. For our QA, only paper matters. That's why we really collect signatures manually after print out. At least QA accepted to use the digital signature feature provide by Adobe Acrobat within a pdf, as collecting physical signatures during the pandemic and with most of the stakeholders working from home was almost impossible.

But once we have exported the document and collected the "manual" signatures on the pdf, we still create a baseline in Jama for the content so that we can do easier comparisons between different document versions.