Pipeline Steps Solutions

Bridge automation

Jira Bridge

Sync selected Flow projects, entities, fields, and workflow statuses with Jira using managed webhooks and visible health checks.

Setup order

  1. Connect Jira with either the OAuth app or an admin email/API-token credential reference.
  2. Map existing Flow projects to existing Jira projects. Project mirroring is not v1 behavior.
  3. Map each Flow entity type to a Jira issue type.
  4. Map fields from Flow and Jira metadata dropdowns. Choose by display name, but save stable Jira ids.
  5. Map statuses separately from fields because Jira status changes use workflow transitions.
  6. Validate setup, then provision webhooks and review health warnings before enabling sync.

Jira auth options

OAuth appRecommended when you want Pipeline Steps to create and maintain Jira webhooks automatically after a Jira admin approves the app.
Admin API tokenFastest for testing direct Jira REST sync through a stored credential reference. Jira webhook automation may still require OAuth or a manual Jira webhook.
SecretsOnly credential references and connection status are shown. API tokens and webhook signing secrets are not displayed in the workspace.

Where to find Jira values

Jira site URLOpen Jira and copy the base address from the browser, for example https://studio.atlassian.net. Do not include project, board, or issue paths.
Jira admin emailUse the Atlassian account email that created the API token. For production, use a dedicated Jira service account when possible.
API tokenCreate it from Atlassian API tokens. Copy it once and store it as a Pipeline Steps secret; do not paste the token into the credential reference field.
Credential referenceThis is the Pipeline Steps secret id created after the token is stored. The reference is safe to show; the token value is not shown again.

Mapping panels

Project mappingSelect existing project pairs before enabling issue creation or updates.
Entity mappingMatches Flow entity types, such as Task or Version, to Jira issue types.
Field mappingUses dropdown metadata so producers see field names while the bridge stores ids like summary or customfield_12345.
Status mappingStores Jira status and transition details. Jira status is not mapped as a normal field.

Advanced JSON details stay collapsed unless your Pipeline Steps implementation contact asks you to review them.

Status transitions

Jira status updates run through workflow transitions. A status pair can still fail when the Jira sync user lacks permission, the workflow has a validator, or no transition exists from the current status to the target status.

What gets monitored

EventsJira events and Flow events are counted separately.
Issue changesCreated Jira issues, updated Jira issues, and updated Flow entities are tracked.
OutcomesSkipped, failed, conflicted, and retry-queue counts help identify work that needs attention.
Required fieldsWarnings call out missing required Jira field mappings before create sync is enabled.
ScreensWarnings call out mapped Jira fields that are not on the create or edit screen.
TransitionsWarnings call out missing Jira status transitions.
Loop preventionBridge-originated events that are skipped are counted so bidirectional sync does not hide loop behavior.
Webhook healthShows current webhook status plus the last successful and failed sync times.
Recent activityShows producer-readable sync summaries without exposing API tokens, signing secrets, or full payload bodies.

Limits to know

Jira permissions, custom required fields, screen schemes, workflow rules, and manual webhook policies can prevent automatic setup. Admin API-token mode can sync through Jira REST, but Jira webhook automation may require OAuth or a manual Jira webhook.

Bidirectional sync is intentionally limited. Comments, attachments, and worklogs stay off unless your Pipeline Steps implementation explicitly enables and tests them.