Incident not visible after failed Data Quality test — run shows “Successful,” Test status = Failed, Incident Status = “New,” but no Incident record

[somg2025]

Affected module
Data Quality → Test execution & Incident creation/visibility

Describe the bug
After executing a Data Quality test, the pipeline run reports “Successful,” the Test Case status is “Failed,” and the Incident Status flips to “New.” However, no incident appears in the Incidents view, and there’s no navigable incident detail from the test case page.

To Reproduce

1. Create any Data Quality test case (e.g., Rule-based or Custom SQL).
2. Execute via ingestion pipeline (source: BigQuery connector).
3. Observe pipeline run result = Successful.
4. Open the test case result: Status = Failed, Incident Status = New.
5. Go to Incidents (or navigate from the test case): no incident listed; no detail page available.

Actual behavior

• Pipeline run = Successful.
• Test Case = Failed with Incident Status = New.
• No incident record visible in Incidents; no working link to details.

Screenshots or steps to reproduce

Expected behavior

• When a test case fails, an Incident should be created and visible, and links from the test case should open the incident detail.
• If incident creation depends on thresholds/severity/config, the UI should clearly indicate what’s missing rather than showing “New” with no record.
• an incident count should be greater than 0 in case of failed cases.

Version:

• OS: : kubernetes , ubuntu
• Python version:3.10
• OpenMetadata version: 1.9.1
• OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==1.9.1]
• Source: BigQuery connector

Additional context
User evaluating Data Quality. One run had ~0% pass / ~100% fail; expected a visible incident for the failure an incident count should be greater than 0

[somg2025]

@TeddyCr I noticed that after I acknowledge or assign an issue, the incident count increments to 1.
Is that by design?
Can incidents be auto-assigned to the team that created the test case?
If this is expected behavior, could we update the documentation to clarify that a new incident can show count = 0 until it’s acknowledged/assigned? That state is a little confusing right now.

[TeddyCr]

Yes, this is by design, We are planning a few improvements here:

• Allow to assign automatically an incident
• Allow to set if an incident should be closed automatically upon successful test case

I'll close this issue for now @somg2025