Skip to content

Jira integration

Connect Threada to Jira for governed issue creation and updates from WorkItems, with auditable workflow handoffs.

Overview

The Jira integration enables Threada to create and update Jira issues as governed actions. WorkItem context — evidence, decisions, and policy outcomes — flows into Jira automatically.

Capabilities

  • Create issues from WorkItem escalations with structured context
  • Apply configured Jira issue updates from governed actions
  • Map projects, issue types, and custom fields
  • Link related WorkItems and evidence to Jira issues
  • Audit trail for every issue operation

A worked example

One end-to-end flow Threada runs with Jira:

  1. A request arrives by email, Slack, or form and becomes a governed WorkItem with a typed schema and cited evidence.
  2. Policy determines the work needs a tracked engineering task, and an approver signs off through an explicit decision step.
  3. Threada creates a Jira issue as a governed action — project, issue type, and fields mapped — with the WorkItem context and evidence attached.
  4. Threada can apply configured Jira updates as governed actions, and every operation is recorded on the WorkItem's audit trail.

Setup

Configure the integration in Studio under pack governance. Use the Atlassian marketplace OAuth path where available, or provide scoped Jira API credentials for deployments using tenant-managed credentials, then map fields to your workflow schema.

  1. In Studio, add the Jira integration under pack governance.
  2. Install through the Atlassian marketplace OAuth path or provide Jira API credentials scoped to the specific projects Threada may write to.
  3. Map Jira projects, issue types, and custom fields to your WorkItem schema.
  4. Validate the connection; the integration activates only after the test write succeeds.

Permissions & data access

Jira can be installed through the Threada-hosted Atlassian marketplace OAuth path or configured with tenant-provided scoped credentials where that deployment path is used.

  • Marketplace OAuth credentials and tenant-provided API tokens are stored in Secret Manager; WorkItems store only runtime integration references.
  • Threada calls Jira's REST API to create issues and apply configured updates; it does not read Jira status back into the WorkItem.
  • Every issue operation runs as a governed action and is recorded on the WorkItem's audit trail.

Frequently asked questions

Does Threada create Jira issues automatically?
Only under policy. Issue creation runs as a governed action, so whether it fires automatically or waits for an approver is decided by your policy overlay. Every issue Threada creates carries the WorkItem context and lands on the audit trail.
Does Threada read Jira transitions back into the WorkItem?
Not currently. Threada writes to Jira — creating issues and applying configured updates as governed actions. Inbound sync of Jira status back into the WorkItem is not supported today.
What access does the integration need?
A scoped Atlassian marketplace OAuth install or Jira API credentials scoped to the specific projects Threada may write to — least privilege. The connection is validated before activation, and every issue operation is logged.
View integration docs