Skip to main content

Sync mapped records to Jira

FlowBridge can write your mapped records straight into Jira Cloud as issues — create-or-update, idempotently — and the DataChord canvas can be embedded right inside a Jira project page so analysts work where their team already lives.

By the end of this page you will have:

  • Stored a Jira Cloud connection in the credential vault.
  • Discovered an issue type's fields and mapped records to issues.
  • (Optionally) installed the Jira panel via the Forge early-access app.
You'll need
  • A Jira Cloud site and an API token.
  • A custom field on your Jira project to hold an external id (for idempotent updates) — e.g. customfield_10042.

Step 1 — Store the Jira connection​

Create a source connection with provider_key = "jira" holding:

{
  "base_url": "https://your-site.atlassian.net",
  "email": "[email protected]",
  "api_token": "…",
  "external_id_field": "customfield_10042"
}

Credentials are encrypted at rest in the vault and only decrypted at sync time.

Step 2 — Point a sync target at Jira​

In your project's sync configuration, choose the jira target and set the object name as "<PROJECT_KEY>:<IssueType>" — for example OPS:Task. DataChord calls Jira's createmeta to discover that issue type's fields (it errors clearly if your configured external-id field isn't present).

Map your target schema's fields to issue fields:

Mapped fieldBecomes
summaryissue summary
descriptionissue description (wrapped in Atlassian Document Format)
issue_typeoverrides the default issue type
customfield_*passed through as-is

Step 3 — Run the sync​

On each batch, DataChord searches Jira (JQL) for an existing issue whose external-id field matches the record's dedup value:

  • found → PUT /rest/api/3/issue/{key} (update)
  • absent → POST /rest/api/3/issue (create)

Rate limits (429) back off automatically; auth failures (401) surface as a clear connection error. Issues are never deleted by a sync.

Step 4 — Embed DataChord in Jira (early access)​

The Forge app under forge-app/ adds a DataChord panel to a Jira project page. After deploying it (forge deploy && forge install), a project admin opens the panel once and pastes a DataChord personal access token. The token stays server-side in Forge; the panel mints a short-lived embed token and renders your mapping projects inside Jira.

Early access

The Forge panel is a working early-access shell. Marketplace listing, 3LO OAuth, and per-Jira-user identity mapping are on the roadmap.

Verify​

  • Running the sync once creates a Jira issue; running it again with the same dedup value updates that issue instead of duplicating it.
  • The Jira panel loads your DataChord project list after a PAT is pasted.

What's next​