Template for Jira

Acceptance Criteria Template for Jira (2026)

Well-written acceptance criteria in Jira bridge the gap between product requirements and QA validation. This template shows how to structure acceptance criteria in Jira using both the Description field and custom fields for maximum traceability.

Consistent acceptance criteria reduce back-and-forth between PMs, engineers, and QA during sprint execution.

Template sections

5 sections covering the complete acceptance criteria workflow.

01

Format Options

Use checklist format for simple criteria: "User can filter results by date range." Use Given/When/Then (Gherkin) format for complex scenarios: "Given a logged-in admin, When they click Delete, Then the item is removed and an audit log entry is created."

02

Jira Configuration

Add a custom text field called "Acceptance Criteria" to your Story issue type screen. This separates criteria from the main Description, making them easier to find during code review and QA. Use Jira automation to flag stories missing this field.

03

Linking to Test Cases

Link acceptance criteria to Jira test cases using Xray or Zephyr. Each criterion maps to one or more test cases. The traceability matrix shows coverage gaps before development starts.

04

Edge Cases

Include negative scenarios and boundary conditions. What happens with empty input? Maximum length? Concurrent users? Network timeout? Edge cases prevent bugs that surface only in production.

05

QA Sign-Off

Add a "QA Approved" status transition in your Jira workflow. QA reviews acceptance criteria before development starts and signs off on completed criteria during testing. This prevents stories from being marked Done without validation.

Copy-paste template

## Acceptance Criteria (Jira custom field)

### Checklist Format
- [ ] User can [action] when [condition]
- [ ] System displays [result] within [timeframe]
- [ ] Error message appears when [invalid input]

### Given/When/Then Format
**Scenario 1: [Happy path]**
Given [precondition]
When [action]
Then [expected result]

**Scenario 2: [Edge case]**
Given [precondition]
When [invalid action]
Then [error handling]

## Jira Fields
- Issue Type: Story
- Acceptance Criteria: [Above content]
- Linked Test Cases: [PROJ-TC-001]

Frequently asked questions

Generate instead of filling in templates

Connect your tools, and Vantage generates the content using real product data. Free to start.

Start the PRD

Writing user stories in Jira? Start with what you're building.

A few sentences is enough: the problem, who has it and what you want to change. Vantage turns it into a structured PRD with requirements you can edit.

0 / 8,000

How this works

  1. We save what you typed. No AI runs on this page.
  2. You create a free account.
  3. Vantage builds a PRD from it inside your own workspace.

Why ask for an account? We’re a small team, and a full generation runs a multi-step AI pipeline that costs us real money. So we tie it to a free account instead of running it anonymously. You also get to keep the result and edit it.

Your text is only used to create your project, and it stays private to your account. If you don’t sign up, we delete it after 7 days. Privacy policy

Free to start. No credit card required.

Related reading