StoryLoop Documentation

Know your pull requests deliver the story

StoryLoop turns a Jira issue's description into testable acceptance criteria, reviews every GitHub pull request against them, and ticks them off in Jira when the code is merged.

A StoryLoop review on a GitHub pull request next to the Jira panel with every criterion ticked off on merge

See it in 45 seconds

From an issue description to criteria ticked off on merge: generate, review the pull request, and confirm the result in Jira.

Playing the video loads it from YouTube. Watch on YouTube ↗

How the loop works

Acceptance criteria get written, then forgotten. Pull requests merge without anyone checking them, and stories close as Done when they aren't. StoryLoop closes that gap in three steps, right inside the Acceptance Criteria panel of every Jira issue.

Step 1

Define

Generate testable acceptance criteria from the issue description, or write them yourself.

Step 2

Verify

Every pull request that mentions the issue key is reviewed against its criteria on each push.

Step 3

Close

Met criteria are ticked off when the pull request merges, so you know when the issue is really finished.

Looking for story writing?

Writing user story descriptions is handled by our dedicated app, StoryCraft AI. StoryCraft writes the story; StoryLoop verifies that the code delivers it.

Key features

Criteria from your description

One click turns a description into a checklist of testable criteria. If the description already lists acceptance criteria, StoryLoop uses those.

Automatic PR reviews

One review comment per pull request, kept up to date on every push, with evidence for each criterion.

Ticked off on merge

Criteria met by a pull request become Done when it merges, with an AI label until someone confirms them.

Merge and workflow gates

A StoryLoop check you can make required in GitHub, and a Jira validator that keeps issues from moving to Done too early.

You have the final say

Change any criterion with one click. StoryLoop never overrides a status set by a person.

Project Context

Describe your product, codebase and terminology once. Every generation and review in the project uses it.

Privacy and data security

  • All AI processing runs on Atlassian's hosted AI service. StoryLoop does not send your issues or code to a third-party AI provider.
  • Acceptance criteria are generated only when someone clicks Generate, and nothing is saved until they click Accept & Save.
  • Pull requests are reviewed only in repositories an administrator has connected.
  • We do not use your Jira data, Project Context or code to train AI models.

Read the full Privacy Policy.