Defect Orchestration

Defect Orchestration is the TestGenie feature that connects failed test executions to Jira defects in a single step — creating a complete, traceable audit trail from defect to execution to test case to requirement.

The Problem It Solves

When a test fails during execution, the natural next step is to log a defect in Jira. But the connection between that defect and the test case that caught it is almost always lost — someone marks the test Failed, plans to link it later, and never does.

The post-mortem then finds an orphaned defect with no test history attached. The auditor finds the same gap.

Defect Orchestration fixes this by making the link a one-step action available immediately when a test is marked Failed — using the link types your project already has, with no manual discipline required.

How It Is Configured

Defect Orchestration is configured in the Defect Orchestration section of the Issue Mapping screen.

Field

What it configures

Defect issue type

Which Jira issue type represents a defect (e.g., Bug)

Defect ↔ Execution

The link type created between the defect and the execution record

Defect ↔ Test Case

The link type created between the defect and the test case that failed

This is a one-time configuration per Jira project. Once saved, the defect link action appears automatically in the Execution Dashboard whenever a test case is marked Failed.

  1. In the Execution Dashboard, find the test case that failed.

  2. Select Failed from the TEST RESULT column.

  3. The ACTIONS column now shows the defect link option for that row.

  4. Click the defect link action.

  5. Search for the existing Jira defect you want to link (by issue key or summary).

  6. Confirm.

TestGenie creates two Jira links:

  • Defect → Execution — using the Defect ↔ Execution link type from Issue Mapping

  • Defect → Test Case — using the Defect ↔ Test Case link type from Issue Mapping

Both are standard Jira issue links, visible in the defect issue's link panel and queryable via JQL.

After linking, the defect issue in Jira shows:

  • A link to the Test Execution issue (e.g., "is caused by KP-88 Sprint 14 Execution")

  • A link to the Test Case issue that caught the defect (e.g., "is tested by KP-42 Verify login with invalid credentials")

From the Test Execution issue, you can navigate to:

  • The defect it triggered

  • The test cases that were run

From the Test Case issue, you can navigate to:

  • The requirement it covers (via Requirement & Test Linkage)

  • The defect it caught (via Defect Orchestration)

This creates a complete chain: Requirement → Test Case → Execution → Defect — fully navigable in standard Jira views.

Frequently Asked Questions

Can I link a defect that hasn't been created yet?
No. The defect link action searches for existing Jira issues. Create the defect issue first, then link it using the ACTIONS column.

Can I link multiple defects to one failed test?
Each failed test execution is linked to one defect via the ACTIONS column. If a test failure reveals multiple defects, link the primary one and note the others in the defect description or as related issues.

What if I linked the wrong defect?
Remove the incorrect link directly from the Jira issue view (standard Jira link removal). The Execution Dashboard does not manage existing links — it only creates them.

The ACTIONS column is not showing the defect link option. Why?
Either the test result is not set to Failed, or the Defect Orchestration section in Issue Mapping is not fully configured. Check both before retrying.