MetaFrazo docsmetafrazo.cloud

Last updated 2026-05-24

How do I connect my Jira workspace?

Connecting a Jira workspace to MetaFrazo is a one-time, two-step flow. You install our app from the Atlassian Marketplace, then click a setup link we send to the installing admin's email. The whole process takes a couple of minutes, and you never share Jira credentials with us.

Who can do this

You need to be a Jira administrator of the workspace you want to connect. Atlassian only lets administrators install Marketplace apps that read event data, and the MetaFrazo organization that gets created during setup will treat you as its first owner.

If you're not the Jira admin, ask the person who is to follow this flow. They can then invite you into the MetaFrazo organization once it exists, with whichever role you need.

Step 1 — install MetaFrazo from the Atlassian Marketplace

  1. Open the Atlassian Marketplace and search for MetaFrazo.
  2. Click Get it now and choose the Jira workspace you want to connect.
  3. Confirm the permission scopes Atlassian asks about. MetaFrazo asks for read-only access to Jira issue events; we never write back to your workspace.
  4. After install, Atlassian shows our app in your Jira settings under Apps → MetaFrazo.

That's the Atlassian side done. We don't need a password from you, and you don't need to set up a separate API token. The trust between MetaFrazo and your Jira workspace is established by Atlassian's own signed app-invocation tokens.

Step 2 — finish setup using the email link

A few seconds after installation, the Atlassian admin who installed the app will receive an email from MetaFrazo with the subject Finish connecting your Jira workspace to MetaFrazo.

The email contains a one-time setup link. Click it.

The setup flow then:

  1. Detects whether you already have a MetaFrazo account.
    • If you do, you sign in.
    • If you don't, you create one — email + password, or sign in with Google / Microsoft if your organization uses one of those identity providers.
  2. Asks you to name the MetaFrazo organization. This is the workspace that will hold your Jira data and your teammates. Pick a name that matches what your colleagues will recognize.
  3. Links the Jira workspace to the new MetaFrazo organization. Both sides confirm the connection at this point: Atlassian re-confirms the app is installed, and MetaFrazo verifies the setup link is fresh and unused.
  4. Logs you in to the MetaFrazo dashboard as the organization's first owner.

The setup link is time-limited and single-use. If you don't click within a few hours, or if you accidentally close the page mid-setup, you can have the email re-sent from the Atlassian app settings under Apps → MetaFrazo → Re-send setup email.

What happens immediately after setup

Once setup completes, the dashboard shows a near-empty state with a banner explaining that MetaFrazo is now listening for Jira events. From that point onward:

  • New Jira events flow in continuously. Anything that happens in your Jira workspace from now on is captured and indexed.
  • Historical events are not backfilled. MetaFrazo does not reach back into your Jira API to import past activity; we only track the events that arrive after the connection is live. This is a deliberate design choice — it keeps your data clean and our security posture defensible.
  • Dashboards populate as data accumulates. Most weekly-rate views need a few days of data to look meaningful; trend views need a few weeks. Single-event views populate immediately.

If a few minutes pass and you don't see any events flowing in at all, Why don't I see any events yet? walks through the most common causes.

Disconnecting later

If you ever want to stop sending Jira events to MetaFrazo, uninstall the app from the Atlassian side — Apps → Manage apps → MetaFrazo → Uninstall. We stop receiving events the moment Atlassian unregisters the app.

Your MetaFrazo organization, your members, and your already-ingested history all stay intact unless you separately delete the organization from the MetaFrazo dashboard. You can reconnect Jira later if you change your mind.

Where to go from here