The title of this documentation page was recently updated, so please update your bookmark!
Integration points between Jira and TM4J allow you to view and manage testing efforts, oftentimes without leaving the issue. From a Jira issue, you can link related traceability/coverage items, such as test cases and cycles, and you can view linked testing results at a glance.
To enable TM4J information to display in Jira, click the TM4J logo on the Jira issue.
The Test Management for Jira section appears.
Depending on the linked and related TM4J items, test-related subsections may appear, as well.
You can disable the TM4J sections on the issue by clicking the Ellipses icon, then Hide Test Management for Jira.
You can view and access traceability links/info by clicking Traceability in the panel on the right side of the page.
Click the Dropdown icon in the issue's Test Management for Jira section, then click Create Test Cycle. The Create Test Cycle screen appears.
Enter your testing information on each of the tabs. (Summaries of each of the tabs are in the latter half of the Creating a Test Cycle topic.)
The Jira issue is automatically linked on the Traceability tab of the new test cycle.
When you're finished adding information to the tabs of the new test cycle, click Save, and the test cycle, along with its status, appears on the Jira issue.
You can define an issue's test coverage by linking existing test cycles to it.
Click the Dropdown icon in the issue's Test Management for Jira section, then click Add Existing Test Cycle.
The selection screen appears, where you can select all of the existing test cycles you want to add to the Jira issue. You can even use the project drop-down list to select and link existing test cycles from other Jira projects.
After you make your selections, click Add, and the test cycle(s) links to and appears on the Jira issue.
If you conduct tests from the Test Player and create new defects or link existing defects, links to the test execution also appear in the Jira defect. This crosslinking allows you to see relationships between Jira defects and related TM4J test efforts without having to navigate back and forth from Jira to the TM4J app. If you do need to make that transition, however, it's as easy as clicking the defect link.
See Run a Test Cycle for more information about working with test-related links in TM4J and Jira.