Affected module

UI + Ingestion Framework (supposedly)

Describe the bug

While OpenMetadata (v1.9.0) partially supports Metabase, critical usability and lineage issues prevent it from being practical.

1. UI Navigation Limitations

• Only Dashboards appear in the Explore tree; Charts (Metabase Models/Questions) are hidden unless accessed through their parent Dashboard.
• Charts reused across multiple Dashboards are not discoverable independently.

2. Incomplete Lineage for Dashboards

• Lineage skips intermediate layers (Models/Questions). Observed flow:
  Database Table ───────► Dashboard (missing Model/Question layer)
• Works correctly in only small percent of cases (as per my initial testing)

3. Missing Chart Lineage

• Charts show empty lineage despite being upstream of Dashboards

Expected behavior

Charts (Metabase Questions / Models) should be first-class citizens:

• Visible in the Explore tree.
• Lineage for Charts should reflect their relationship to source tables and Dashboards:
  Database Table ──► Model/Question ──► Dashboard

To Reproduce
In Metabase create a model, a question based on the model, a question based on the question and add all that to two different dashboards. Add Metabase as a Dashboard service into OMD.

Version:

• OpenMetadata version: 1.9.0

Additional context

Are there architectural constraints to representing Charts (Metabase Questions/Models) as independent entities?
Probably the team has existing plans/designs for this?
Would a PR addressing these issues be welcomed?