What counts as a decision in Jira?

Acceptance criteria and scope calls in ticket descriptions and closing comments: the statements that change what ships. Status noise and routine updates don't become decisions; extracted candidates still need a human to confirm them.

Does Lockstep write to our Jira tickets?

No. The connection is read-only and scoped to the projects you connect. Binding decisions live in Lockstep's record, each linked back to the ticket it came from.

How do I connect Jira to Lockstep?

From the Connections page in the Lockstep dashboard. Connect Jira once for your org, then allowlist the projects to read by project key. Only those projects are read.

Lockstep for Jira

Decisions made in Jira tickets, comments, and status changes become part of Lockstep’s binding decision record, delivered to the humans and agents doing the work.

What Lockstep captures from Jira

acceptance-criteria changes on a story
a scope decision recorded in ticket comments
a priority call that changes what ships

How the loop runs

Lockstep captures the decision from Jira, routes it to its owner for one-click confirmation that makes it binding, then briefs every engineer and every AI coding agent before they touch the code, and flags any pull request that drifts from it. See the full pipeline on how it works.

How to set up Lockstep for Jira

In the Lockstep dashboard, open Connections, pick Jira, and connect it with read-only OAuth.
Allowlist the projects Lockstep should read, by project key (for example PLATFORM).
Lockstep watches description changes and tickets moving to Done, and drafts acceptance-criteria and scope calls as candidate decisions.
The owner confirms, edits, or rejects each draft. Owners can tighten the wording or narrow the scope first; the confirmed text is what gets enforced, and it links back to the ticket it came from.
Engineers and agents on the affected code are briefed, and the PR check flags changes that conflict.

Example: a decision captured from Jira

Illustrative example

In Jira

Closing comment on PLATFORM-412: "Agreed with design: bulk invite ships without CSV upload this release. Manual entry only, max 50 emails."

Drafted decision

Bulk invite v1 supports manual entry of up to 50 emails; CSV upload is out of scope for this release. Source: PLATFORM-412.

Approved record

The ticket's owner confirms it. The scope call is binding and linked to PLATFORM-412, so an agent asked to add CSV import starts the session knowing it was cut. If the call changes next release, the old decision is superseded with lineage, not edited in place.

Access & trust

Read-only OAuth. Scoped to the projects you connect.

What Lockstep reads

Tickets in the projects you connect: descriptions, comments, and status changes

What Lockstep never does

Projects you haven't connected
Writing to your tickets: no comments, transitions, or field edits
Making anything binding on its own: every candidate waits for a human to confirm it
Storing secrets: tokens, keys, and credential-shaped strings are redacted at ingestion

Full details on the security page.

Frequently asked questions

What counts as a decision in Jira?: Acceptance criteria and scope calls in ticket descriptions and closing comments: the statements that change what ships. Status noise and routine updates don't become decisions; extracted candidates still need a human to confirm them.
Does Lockstep write to our Jira tickets?: No. The connection is read-only and scoped to the projects you connect. Binding decisions live in Lockstep's record, each linked back to the ticket it came from.
How do I connect Jira to Lockstep?: From the Connections page in the Lockstep dashboard. Connect Jira once for your org, then allowlist the projects to read by project key. Only those projects are read.