← All integrations

GroundTruth keeps Jira accurate to your codebase. It reads your issues and their acceptance criteria, links each to the branches and pull requests that implement it, and moves the ticket to the right status, only when the work and the criteria agree.

What we read

• Issues across your projects: summary, type, status and status category, assignee, parent, and last-updated.
• The description, with Atlassian Document Format flattened to plain text so acceptance criteria are readable.
• Native Jira task-list checkboxes as verifiable acceptance criteria: an unchecked box blocks auto-close.
• Sub-task and epic hierarchy, so team and initiative scoping is accurate.

What we write back

Real Jira transitions, not a silent field poke. We fetch the transitions available on the issue and apply the one that matches the correct status category, so your workflow rules and post-functions run exactly as they would for a human. Every write is recorded in the audit chain with the prior value, and can be reverted.

Acceptance-criteria gate

A merged pull request never auto-closes an issue whose acceptance criteria are unmet. If any checkbox criterion is unchecked, or a text or Given/When/Then criterion still needs verification, the issue moves to in_review instead of done, and is flagged for a human.

Setup

1. Connect via Atlassian OAuth (3LO), or with an API token plus the account email for Basic auth.
2. Your site URL is the endpoint (for example acme.atlassian.net); pick the project keys to sync.
3. We backfill open issues, then keep them current from webhooks.

Continuous sync

Point a Jira automation or webhook for issue created and updated events at the URL we give you on connect. Clear cases reconcile automatically; ambiguous ones wait for a human.

Status mapping

Names are examples. We read your project's real status category, and the target status name is configurable per workflow.