Skip to content

File a tracker issue

Files a Linear or Jira issue from a title and description, with external writes held for approval under the default autonomy policy.

Template create-issue
Works on An issue tracker (Linear or Jira)
Where a person acts Approve issue creation — a person approves or rejects, waiting up to 24h

Drawn from the template spec at build time. Bookkeeping nodes that only record status are left out; amber nodes are where a person acts.

flowchart TD
  n_publishOutcome["Publish outcome"]
  n_checkAuto{"Check auto?"}
  n_humanApproval>"Approve issue creation<br/><small>person: approval</small>"]
  n_autoWrite["Auto write"]
  n_manualWrite["Manual write"]
  n_doneRejected(["Done<br/><small>done rejected</small>"])
  n_done(["Done"])
  n_publishOutcome --> n_checkAuto
  n_checkAuto -->|"yes"| n_humanApproval
  n_checkAuto -->|"no"| n_autoWrite
  n_humanApproval -->|"approved"| n_manualWrite
  n_humanApproval -->|"rejected"| n_doneRejected
  n_humanApproval -->|"timed out"| n_doneRejected
  n_autoWrite --> n_done
  n_manualWrite --> n_done
  class n_humanApproval gate

Seeded content rather than a proven flow. The connector, the agents, and the governance it relies on exist, but only the engineering flow has a complete, exercised end-to-end path today. See product overview §8.

Every built-in template is seeded into the workflow library and can be cloned, edited on the visual canvas, and versioned — see architecture for the node types. The spec lives in packages/shared/src/workflow/templates/createIssue.ts.

© 2026 Jorge Barnaby

Source-available under FSL-1.1-MIT

Source on GitHub

Built with Astro and Starlight