The Issue Mapping screen is where you configure TestGenie for your Jira project. It is a one-time setup that tells TestGenie which of your existing Jira issue types and link types correspond to each role in the test management lifecycle.
Open Issue Mapping from the TestGenie navigation sidebar, or click Start Configuring on the Get Started screen.
Overview
Issue Mapping has three sections arranged in a two-column layout:
Left column | Right column |
|---|
Requirement & Test Linkage | Execution Planning |
Defect Orchestration | Automated Validation info panel |
All fields use dropdowns populated with the issue types and link types already present in your Jira project. No new issue types are created. Nothing in your project changes.
Click Save Changes when all sections are complete. Changes take effect immediately.
Section 1: Requirement & Test Linkage
This section maps the issue types and link types used for requirements, test cases, test steps, and preconditions.
Field | Description | Example |
|---|
Requirement issue type | The Jira issue type that represents a requirement — the thing being tested | Story, Feature, Epic |
Test Case issue type | The issue type used for test cases generated by TestGenie | Task, or a custom "Test Case" type |
Req ↔ Test Case link type | The link type that connects a requirement issue to its test cases | "is tested by", "Relates to" |
The Requirement & Test Linkage section is also used by the Rovo agent during AI generation. When you launch generation from a Jira issue, the agent checks this configuration to identify whether the issue is a valid requirement type.
Note: The full TCMConfig also stores testStepIssueType, preconditionIssueType, and testToPreconditionLinkType — these are set by the Rovo agent during configuration conversations and used when creating test step child issues and precondition links.
Section 2: Defect Orchestration
This section configures how failed test executions are connected to Jira defects. Once configured, linking a failed test to a defect is a single action in the Execution Dashboard.
Field | Description | Example |
|---|
Defect issue type | The Jira issue type used for defects or bugs | Bug |
Defect ↔ Execution | The link type connecting a defect to the execution record where it was found | "is caused by", "Blocks" |
Defect ↔ Test Case | The link type connecting a defect to the test case that caught it | "is tested by", "Relates to" |
If this section is left empty, the ACTIONS column (defect link action) will not appear in the Execution Dashboard.
Section 3: Execution Planning
This section configures the test plan and execution issue types and all the link relationships between them. It also contains the Enable Test Execution tracking checkbox, which must be checked for pass/fail tracking to work.
Field | Description | Example |
|---|
Test Plan issue type | The issue type used for test plans | Epic, or a custom "Test Plan" type |
Test Execution issue type | The issue type used for execution records (one per run) | Task, or a custom "Test Execution" type |
Enable Test Execution tracking | Checkbox — must be enabled to track Passed / Failed / Not Executed results in the Execution Dashboard | ✓ checked |
Plan ↔ Test Case | Link type between a test plan and the test cases it contains | "Relates to", "includes" |
Plan ↔ Execution | Link type between a test plan and its execution run issues | "Relates to", "spawns" |
Execution ↔ Test Case | Link type between an execution run and each test case it covers | "Relates to", "covers" |
Important: If Enable Test Execution tracking is not checked, the TEST RESULT column in the Execution Dashboard will not be interactive and results cannot be recorded.
Saving Configuration
Click Save Changes in the bottom-right corner. A success notification confirms the configuration has been saved.
If the save fails, check that:
The project key was detected correctly (shown in the page header)
All required dropdowns have a selected value
Your Jira user has permission to write project properties
Tips
You can use the same link type (e.g., "Relates to") across multiple fields if your project does not have specialised link types. The important distinction is which field it appears in, not the link name.
Configuration is stored per Jira project. Different projects can have different configurations.
You can update configuration at any time. Changes to Execution Planning take effect on the next execution run — existing runs are not affected.
The Automated Validation info panel on the right is informational only — it confirms that the mapping you have defined will enable traceability across the test lifecycle.