Why don't I see any events yet?

After you finish connecting your Jira workspace, the dashboard should start populating within a few minutes. If a longer pause goes by and your visuals are still empty, walk through the checks below. The cause is almost always one of three things, and each one is something you can fix yourself.

Quick sanity check before troubleshooting

Two things to confirm before diving in:

• Has anything actually happened in Jira since you installed? MetaFrazo starts capturing events from the moment the app installs; we do not reach back to import historical activity. If your Jira workspace was quiet for the last hour, there are simply no events to show. Create or transition a test issue, then wait two minutes.
• Are you looking at the right MetaFrazo organization? The organization selector in the dashboard's top-right shows which organization you're viewing. If you belong to several organizations, double-check you're not staring at an empty one.

If both of those are fine and the visuals are still empty, the issue is somewhere in the connection itself.

Check 1 — Confirm the MetaFrazo app is enabled in Jira

Open your Jira workspace and go to Apps → Manage your apps → User-installed apps. The MetaFrazo app should be listed with status Enabled.

If it shows Disabled, Suspended, or Pending license review, click the app and re-enable it. Atlassian occasionally puts apps into a maintenance state — for example, after a workspace-wide settings change — and stops dispatching events until you re-enable.

If the app isn't listed at all, the installation was rolled back. Re-install from the Atlassian Marketplace and re-run the setup flow.

Check 2 — Open the MetaFrazo Integrations tile

In the MetaFrazo dashboard, navigate to the Integrations view (sidebar → Integrations). The Jira connector tile shows:

• Last heartbeat — a "MetaFrazo received a check-in from your Jira workspace" timestamp. The app sends one every few minutes. If this timestamp is recent, the connection is healthy and the cause of missing events is elsewhere (most likely Check 3).
• Event counters — how many events arrived, how many were queued, and the most recent error category if any. If you see a non-zero error count, the tile shows the most recent error code so you can recognize it.
• Last error — the most recent error your installation has hit, if any. Most errors are transient (Jira API quotas, brief network blips) and self-recover within a few minutes.

If the last heartbeat is more than an hour old, the connection has gone quiet. Try a hard re-install: uninstall the app from Jira, install it again from the Marketplace, and re-run setup. This restores the connection in roughly a minute.

Check 3 — Verify Jira is actually producing the events you expect

Some Jira configurations restrict which events fire externally. Common reasons your workspace might be quiet even when people are working:

• Project-level event suppression. A Jira admin may have disabled webhook dispatch for specific projects. Open Project settings → Notifications for the project where you expected activity and confirm event dispatch is enabled.
• Issue-security-level restrictions. Some Jira configurations only emit events for issues at certain security levels. If your work is on a restricted security level, MetaFrazo won't see it.
• A quiet workspace. Tickets get created, but the rest of the activity (transitions, assignments, configuration changes, sprint movement) is what generates the bulk of MetaFrazo's visuals. If your workspace mostly stays at issue creation, expect sparse dashboards.

If you've confirmed event dispatch is enabled and your workspace is genuinely producing transition / assignment / configuration events, but MetaFrazo still shows nothing, your Atlassian admin can check Apps → Audit log in Jira for entries from the MetaFrazo app — those entries confirm whether Atlassian is dispatching to us or refusing.

What you can expect from each visual once events do flow in

Some visuals need more time to look meaningful than others:

• Single-event views (recent transitions, recent configuration changes) populate within minutes of the first events arriving.
• Daily and weekly counters (Total transitions, Reopen rate) populate over the first 24 hours.
• Trend views (Backlog acceleration, Risk escalation, Forecast indicators) need at least two to four weeks of data to surface meaningful patterns.
• Compliance evidence views mature over a quarter — that's the timeframe most auditors care about.

If your dashboard looks sparse after two days, that's expected. If it still looks sparse after two weeks of normal Jira activity, contact support from inside the dashboard (top-right menu → Contact support) so we can take a look.

Where to go from here

• How do I connect my Jira workspace? — the original setup flow.
• What is MetaFrazo? — what dashboards you'll see once events start flowing.