Jump go di content

Integration with Jira

Connect Threada to Jira make e fit create and update issue dem from WorkItem as action wey get governance, with workflow handoff wey you fit audit.

Overview

Di Jira integration dey make Threada fit create and update Jira issue dem as action wey get governance. WorkItem context — evidence, decision, and policy outcome — dey flow enter Jira by itself.

Wetin e fit do

  • Create issue dem from WorkItem escalation with structured context
  • Update Jira issue dem — add comment and drive transition — from action dem wey get governance
  • Map project dem, issue type and custom field
  • Link WorkItem and evidence dem wey relate go Jira issue
  • Audit trail for every issue operation wey happen

One example wey dem work through

One end-to-end flow wey Threada dey run with Jira:

  1. Request dey enter by email, Slack, abi form and e dey become WorkItem wey get governance with typed schema and cited evidence.
  2. Policy dey decide say di work need engineering task wey dem dey track, and approver dey sign off through one explicit decision step.
  3. Threada dey create Jira issue as action wey get governance — project, issue type, and field dem wey dem map — with di WorkItem context and evidence join am.
  4. Threada fit drive Jira issue transition dem as action wey get governance, and we dey record every operation for di WorkItem audit trail.

Setup

Set di integration for Studio under pack governance. Provide Jira API credential dem wey get project-scoped permission, and map field dem go your workflow schema.

  1. For Studio, add di Jira integration under pack governance.
  2. Provide Jira API credential dem wey dem scope to di specific project dem wey Threada fit write to.
  3. Map Jira project dem, issue type and custom field go your WorkItem schema.
  4. Validate di connection; di integration go only activate after di test write don succeed.

Permission plus data access

Jira dey use credential dem wey you provide — no be OAuth app wey Threada dey host.

  • Threada dey authenticate with one Jira API token wey you supply, wey dem scope to di specific project dem wey e fit write to, wey dem store for Secret Manager.
  • Threada dey call Jira REST API to create and update issue dem and drive transition dem; e no dey read Jira status back into di WorkItem.
  • Every issue operation dey run as action wey get governance, and dem dey record am for di WorkItem audit trail.

Question dem wey people dey always ask

Threada dey create Jira issue by itself?
Na under policy only. Issue creation dey run as action wey get governance, so weda e go fire by itself or wait for approver na your policy overlay go decide. Every issue wey Threada create dey carry di WorkItem context and e dey land for di audit trail.
Threada dey read Jira transition dem back into di WorkItem?
Not for now. Threada dey write to Jira — e dey create issue dem, add comment, and drive transition as action wey get governance. Inbound sync wey go carry Jira status back into di WorkItem no dey supported today.
Wetin access di integration need?
Jira API credential dem wey dem scope to di specific project dem wey Threada fit write to — least privilege. We dey validate di connection before we activate am, and we dey log every issue operation.
See integration docs