§ 07 · DOCS

Jira integration

Assign a Jira Cloud ticket to an AI developer or AI tester by custom field, label or Slack, and track it to done.

Awks (agentic workers) are AI developers and testers that build and test your work items. A Jira ticket is one kind of work item (you can also hand an awk work by asking in Slack). With Jira connected, awks pick tickets up from Jira Cloud, track progress, and transition statuses automatically.

Connecting Jira

In the console's Integrations step, install the Awk Jira app on your Jira Cloud site (this needs a Jira site admin), authorise with Atlassian, and select which projects the agentic workers can see.

The team's Jira card in the console showing the connected project picker and a per-project workflow-status auto-detect control — The team's Jira card — pick which projects agentic workers can see, with per-project workflow-status auto-detect. (Example data.)

Jira Server and Data Center are not currently supported.

Assigning tickets to agentic workers

There are three ways to tell an agentic worker to pick up a Jira ticket.

Method 1: Custom field

Add a single-choice select field called Awk Assignee to your Jira project.

Company-managed projects:

→Go to Jira settings → Issues → Custom fields and click Create custom field
→Choose Select List (single choice), name it Awk Assignee, and add the options OG and QA
→Add the field to your project's issue screens

Team-managed projects:

→Go to Project settings → Issue types and pick the issue type
→Add a Dropdown field named Awk Assignee with the options OG and QA

To assign a ticket, set the field to the agentic worker's name:

Field value	Agentic worker
`OG`	OG picks up the ticket
`QA`	QA checks the build against the ticket

The ticket also needs to be in one of the trigger statuses you map in the console (see Status transitions) — agentic workers only pick up tickets from those statuses.

This is the recommended method for teams that want structured, automated assignment.

Method 2: Labels

Add a label to the Jira ticket:

Label	Agentic worker
`awk:og`	OG picks up the ticket
`awk:qa`	QA checks the build against the ticket

As with the custom field, the ticket also needs to be in one of the trigger statuses you map in the console (see Status transitions).

Labels are simpler to set up but less structured. Use this method if you don't want to add custom fields to your project.

Method 3: Ask in Slack

You can also tell an agentic worker to pick up a specific ticket directly:

@OG-Awk pick up PROJ-318

The agentic worker reads the ticket and starts working.

What happens next

When OG picks up a ticket:

→Reads the ticket description and acceptance criteria
→Opens a Slack thread to confirm requirements with the reporter
→Writes code in a new branch
→Runs tests and iterates until green, then puts the change through a code review
→Opens a pull request on GitHub
→Transitions the Jira ticket to In Review
→Hands off to QA, when independent QA is requested, to check the build against the ticket

When independent QA is requested, QA checks the build does what the ticket asked. If it finds issues — the build doesn't meet the requirement, a regression, a security risk — it sends the work back to OG with its findings. OG fixes and resubmits. When QA passes it, the ticket moves to Done. OG finishes the work, and merging the pull request waits for your approval in Slack.

Status transitions

Agentic workers use standard Jira statuses:

Status	Meaning
To Do	Ticket is waiting to be picked up
In Progress	OG is actively working on it
In Review	QA is testing the build, when independent QA is requested
Done	QA passed the build, when independent QA is requested — merging the PR still needs your approval

Your Jira workflow needs these statuses (or equivalents) with transitions between them.

You map each transition for each agentic worker in the console — the status a ticket moves to on pickup, on pass, on fail, on cancel, and on handoff — so the agentic workers drive your board exactly the way your team already works.

The Jira workflow mapping for each agentic worker in the console with OG and QA columns configuring pickup, pass, fail, cancel, and handoff status transitions — Workflow mapping for each agentic worker — the Jira statuses OG and QA move a ticket through on pickup, pass, fail, cancel, and handoff. (Example data.)

Tips for better results

→Write clear acceptance criteria — the more specific, the better OG's first attempt will be
→Link relevant code — mention file paths, modules, or existing patterns in the ticket description
→Specify the branch — if you want work done on a specific branch, say so in the ticket
→One feature per ticket — agentic workers work best on focused, well-scoped tickets