— INTEGRATION · JIRA · PROJECT-SCOPED

Cyborgs that work tickets in Jira.

Pick up issues, transition states, log work, comment, link PRs. Engineer Cyborg + Jira = sprint flow without a sprint master breathing down anyone’s neck.

Both flavours supported

Jira Cloud + Jira Data Center (self-hosted). For Data Center, use Personal Access Tokens with project-scoped permissions.

— 02 / CAPABILITIES

— WHAT THE CYBORG CAN DO IN JIRA

Capabilities · scoped, audited.

CAP · READ

Read boards + sprints + issues

Reads only authorised projects. Issue details, custom fields, attachments, links, history.

  • Issue + epic structure
  • Custom fields (read)
  • Sprint planning
  • Backlog
CAP · WORK

Pick up + transition

Self-assigns from sprint backlog (per role rules). Transitions through workflow with comments.

  • Self-assign
  • Workflow transitions
  • Status comments
  • Re-estimate
CAP · LOG

Log work + time

Logs hours worked, estimates remaining, fills custom fields, attaches deliverables (PRs, designs, docs).

  • Worklog entries
  • Time tracking
  • Custom-field updates
  • Attachment + link
CAP · LINK

Link PRs + commits

Auto-links to GitHub/GitLab PRs via Smart Commits. Updates issue status when PR merges.

  • Smart Commits
  • PR / MR auto-link
  • CI status mirroring
  • Auto-close on merge

03Auth + scopes.

  • Jira Cloud: OAuth 2.0 (3LO). Scopes: read:jira-work, write:jira-work, read:jira-user.
  • Jira Data Center: Personal Access Token with project-scoped permissions (Browse, Edit, Transition, Add Comments, Log Work).
  • Project-level access enforced by Cyborg dashboard via project permissions.

04Setup · 3 minutes.

  • Step 01 · Connect Atlassian (Cloud) or paste PAT (Data Center).
  • Step 02 · Pick projects + boards the Cyborg should work on.
  • Step 03 · Configure self-assignment rules (which JQL queries Cyborg pulls from).
  • Step 04 · Cyborg picks up its first issue within a sprint cycle.

05FAQ.

Workflow customisations supported?+

Yes. The Cyborg discovers your custom workflow on first connect and respects valid transitions. Custom fields (text, select, etc.) are read/write where the Cyborg has permission.

Jira Service Management?+

Supported. Customer-Support and Operations Cyborgs work in JSM — triage, response drafting, SLA tracking. Customer-portal-side actions are roadmap (v0.3.x).

Can Cyborg create epics?+

Yes, with Manager-level approval (T3). Cyborg can also break epics into stories + subtasks if you grant that permission.