An integration shows Connected but dashboards aren't filling in. Here's the diagnostic order to follow.
Step 1 — Has the initial sync actually finished?
Connected and Synced are different. The integration card surfaces both. Wait for the initial backfill to finish before assuming data is missing.
Step 2 — Is the time period covered by your plan's history depth?
Some plans only ingest the last 30/60/90 days. If you set the dashboard date range to "Last 12 months" but your plan covers 90 days, the older portion shows empty.
Step 3 — Did you select the right resources?
For source-control integrations: confirm the relevant repositories are in the selection list.
For planning integrations: confirm the relevant projects/teams are selected.
For communication integrations: confirm the channels you care about are included.
Step 4 — Are status mappings configured?
For Jira and similar tools, cycle time and WIP need active vs. waiting state classification. If statuses aren't mapped, those metrics stay empty even when issue data is present.
Open the integration's status mapping inside Administration → Productivity Tools and verify each status is classified.
Step 5 — Are users mapped?
If GitHub users haven't been mapped to Leanmote teammates, per-team metrics may show empty even though raw activity is captured. See Users management for mapping steps.
Step 6 — Is the data source accidentally excluded?
Filters on the dashboard or View can hide data. Reset filters to verify whether the issue is filter-side or sync-side.
Common confusing patterns
A metric shows zero only on weekends — your workweek setting may be excluding the days. Check Organization Settings.
A metric shows empty only for one team — that team's mapping or status classification likely needs attention, not the integration.
Related articles
Sync isn't completing
Why a metric looks off
Users management
Plan limits and history depth