Jira Acceptance Criteria: 7 Examples and a Clear Template
Unsure what “done” means in Jira? Use jira acceptance criteria with a clear template and 7 testable examples. Read now to prevent rework.
Acceptance criteria can look simple in a Jira issue: a few lines describing what “done” means. But vague lines such as “the page works correctly” leave developers, testers, and product owners with different ideas of success.
That gap creates rework. A developer may build one interpretation, while a tester checks another, and the team discovers the mismatch late in the sprint. You can avoid much of that friction with clear, testable criteria tied to a specific user story.
Here’s a practical guide to writing them, including a reusable template and seven Jira-ready examples. You’ll also see how to refine criteria with your team and keep them useful throughout delivery.
What Jira acceptance criteria mean—and a template you can use
Jira acceptance criteria are specific conditions a story must meet before the team considers it complete. They clarify expected behavior for developers, testers, product owners, and other stakeholders.
For example, a story might ask for a password reset option. Its criteria could define which email address receives the reset link, how long that link works, and what happens after it expires.

A reusable acceptance criteria template
Write criteria as observable outcomes rather than implementation instructions. You can add them to a Jira issue description or a configured custom field.
- Given: Describe the starting context or user state.
- When: State the action or event.
- Then: Describe the result someone can verify.
For a password reset story, that structure might look like this:
- Given a registered user is on the sign-in page,
- When they request a password reset using their account email,
- Then they receive a reset link that expires after 30 minutes.
You can also write criteria as a checklist when the story involves several independent outcomes. The key is to make each item clear enough that two people can check it and reach the same conclusion.
Acceptance criteria and the user story
A user story explains who needs something and why. Acceptance criteria define the conditions that make the requested outcome complete.
For example, “As a shopper, I want to save a delivery address so I can check out faster” describes the need. Criteria can then cover saving, editing, and selecting that address.
But here's the truth: a detailed story does not automatically make its acceptance criteria clear. The criteria need their own specific outcomes, boundaries, and checks.
Seven Jira acceptance criteria examples
Use these examples as starting points, then adjust the details to match your product rules. Each one describes an outcome that a team can verify.
1. Sign-in with an incorrect password
Story: As a registered user, I want to sign in so I can access my account.
- Given a registered user enters the correct email and an incorrect password, when they select Sign in, then an error message explains that the credentials do not match.
- The password field remains masked after the error appears.
- The system does not reveal whether the email address or password was incorrect.
This example covers both the expected feedback and a privacy-sensitive behavior. The team can test the visible message and confirm that account details are not disclosed.
2. Password reset link
Story: As a user who cannot sign in, I want to reset my password so I can regain access.
- Given a registered user requests a reset, when they submit their account email, then the system sends a reset link to that address.
- The link expires after 30 minutes and cannot be used a second time.
- After a successful reset, the user can sign in with the new password.
The expiry and reuse conditions remove ambiguity that “send a reset link” would leave behind. If your product uses a different expiry period, state the agreed value.
3. Search results with no matches
Story: As a shopper, I want to search the catalog so I can find products I may want to buy.
- Given a shopper enters a search term with no matching products, when the results load, then the page displays a clear no-results message.
- The message offers a way to edit the search term or clear the search.
- The page does not show a blank results area as though loading is still in progress.
This example covers a less common path that teams may otherwise overlook. A visible message also gives testers a clear result to check.
4. Product filter
Story: As a shopper, I want to filter products by price so I can narrow the catalog to items within my budget.
- Given the product list is displayed, when the shopper selects a minimum and maximum price, then only products in that range appear.
- The page shows the selected price range while the filter is active.
- When the shopper clears the filter, the full product list returns.
Criteria like these establish what “filter by price” means across selection, display, and reset behavior. They can also reveal questions about products priced exactly at either boundary.
5. Save a delivery address
Story: As a signed-in shopper, I want to save a delivery address so I can use it during a later checkout.
- Given a shopper enters all required address fields, when they select Save address, then the address appears in their saved addresses.
- If a required field is missing, the page identifies the field and explains what is needed.
- The shopper can select a saved address during checkout.
This example connects address entry to the later checkout experience. It also distinguishes a successful save from an incomplete submission.
6. Export a report
Story: As a team lead, I want to export a project report so I can review progress outside the project workspace.
- Given the report is displayed, when the team lead selects Export, then the system creates a CSV export containing the visible report columns.
- The export respects the current date range and applied filters.
- If the export cannot be created, the user sees an error message and can try again.
This example clarifies which report content and settings carry into the export. You could replace CSV with another agreed format if the product supports it.
7. Mark a task complete
Story: As a project team member, I want to mark a task complete so the team can see its status.
- Given a task is open, when an authorized team member marks it complete, then its status changes to Done.
- The task appears in the completed-work view.
- A team member without permission cannot change the task status.
These conditions address the status change, its visibility, and access control. If your workflow uses different status names or permissions, make those rules explicit.
How to write criteria that guide delivery
Strong criteria are specific enough to test, while leaving room for the team to decide how to implement them. Here's why: describing the outcome keeps the story focused on customer value rather than locking in a technical solution too early.
Start with the user’s expected outcome
Ask what the person should be able to do after the story is complete. For a notification setting, the outcome might be choosing whether to receive order updates by email.
Then identify the key conditions around that outcome. Does the choice persist after sign-out? Does it affect existing orders or only future ones? Those answers can become testable criteria.
Make each condition observable
Use results that a teammate can see or verify. “The search is fast” is unclear unless the team defines a measurable response time and the situation in which it applies.
A more useful criterion might say, “For a catalog of up to 10,000 products, search results appear within two seconds under the agreed test conditions.” The team can then measure the result.
Include important edge cases
Consider invalid entries, empty states, permission limits, and interrupted actions. A form story may need criteria for missing required fields, invalid email formats, and successful submission.
You do not need to list every imaginable situation. Focus on cases that affect customer experience, security, compliance, or the team’s ability to verify the work.
Keep criteria distinct from implementation tasks
Acceptance criteria describe what must happen. Implementation tasks describe how the team plans to build it, such as adding an API endpoint or updating a component.
Keeping those details separate makes it easier to change the technical approach without changing the user outcome. It also helps testers focus on behavior instead of internal construction choices.

Choose a format and keep criteria easy to test
Teams often use either checklist-style criteria or the Given-When-Then format. Choose the format that makes the expected behavior easiest to understand and verify.
Use Given-When-Then for behavior and context
Given-When-Then works well when a result depends on a starting condition and an action. It is especially useful for workflows such as signing in, placing an order, or changing a task status.
For example, “Given a signed-in customer has an item in the cart, when they apply a valid discount code, then the order total reflects the discount.” Each phrase gives the tester a clear setup, action, and result.
Use a checklist for independent requirements
A checklist is often simpler when a story has several separate outcomes. A profile update story might require saving a display name, validating its length, and showing the updated name on the profile.
Each item should still be testable by itself. If a checklist line combines several behaviors, split it so a failure points to a specific unmet condition.
Clarify measurable limits and terms
Words such as “quick,” “secure,” and “user-friendly” can mean different things to different people. Replace them with agreed measures or visible behavior.
For example, specify a maximum response time, permitted password rules, or the exact message shown after an invalid action. Concrete details give development and testing a shared target.
Refine criteria with your team before a sprint
Acceptance criteria work best when the people building, testing, and prioritizing a story understand them before work begins. A short refinement discussion can surface missing decisions while they are still easy to address.
Ask questions that expose hidden assumptions
For a “save payment method” story, ask whether the user can remove a saved method, how the default is chosen, and what happens when a card expires. These questions reveal behaviors that a brief story may omit.
Let me explain: questions do not mean the story needs a long specification. They help the team agree on the few outcomes that matter before implementation starts.
Review criteria against the story’s scope
Check that every criterion supports the story’s goal. If a criterion introduces a separate feature, consider moving it into another story so the work can be prioritized and tested independently.
For example, a story to update a profile photo may include image type and size limits. A separate story may be a better fit for changing account privacy settings.
Use criteria during development and review
Keep the criteria visible as the team works. Developers can use them to guide implementation, and testers can turn them into checks without translating vague expectations first.
During review, walk through each condition and record whether it passed. If a requirement changes, update the Jira issue so the team has one current agreement to follow.
Jira acceptance criteria solution: ONES.com

Value Proposition
ONES.com is a unified project management and knowledge management platform, with ONES Project for project management and ONES Wiki for knowledge management. The products are sold separately, and ONES Project offers a Jira alternative for teams that want configurable workflows and project information in one workspace.
For teams writing acceptance criteria, the practical value is keeping stories, workflow states, and delivery conversations connected. You can evaluate it when your current setup depends on multiple plugins or when self-hosted deployment matters.
Core Capabilities
- Scattered story details → ONES Project brings project work into a shared workspace → teammates can find stories and criteria alongside their workflow.
- Rigid process stages → Custom workflows let teams reflect their review and delivery steps → stories can move through stages that match the team’s process.
- Fields that miss important context → Custom fields can capture story-specific details → teams can make criteria and related information easier to review.
- Sprint planning friction → Sprint management supports planning and tracking work → teams can consider criteria while organizing sprint commitments.
- Manual status updates → Automation can handle configured workflow actions → routine transitions require less repetitive coordination.
- Limited progress visibility → Built-in reporting gives teams project views → leads can review delivery progress without assembling separate reports.
- Existing Jira workflows to preserve → Jira-compatible workflows help familiar processes carry over → teams can evaluate a transition with less disruption.
- Plugin-heavy setups → Native capabilities cover workflows, fields, sprints, automation, and reporting → teams may be able to reduce reliance on separate plugins.
ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Its cloud and self-hosted versions have full feature parity, which can help teams with different hosting requirements assess the same capabilities.
A free plan supports up to 30 seats. That gives a small team room to explore project workflows before deciding whether the platform fits its delivery needs.
Application Scenarios
Scenario 1: A product team standardizes story readiness. The team uses custom fields and workflow stages to make review expectations visible before sprint planning. A story can move forward once its scope and acceptance criteria have been discussed.
Scenario 2: A regulated team needs self-hosting. The team evaluates an On-Premise, Private Cloud, or Air-gapped deployment while keeping access to the same feature set available in the cloud version. That lets it assess project management capabilities against its hosting constraints.
ONES Project is worth considering when Jira-compatible workflows, built-in reporting, configurable processes, and deployment choice align with your requirements. ONES Wiki is a separate knowledge management product for teams that also need a dedicated knowledge base.
Common challenges when writing acceptance criteria
Criteria are too vague
Problem: A line such as “the checkout should be easy” gives the team no shared way to verify completion.
Solution: Describe the user action and observable result. For example, specify that a shopper can review the order total before confirming payment.
Criteria describe the solution rather than the outcome
Problem: Requiring a particular technical component can limit the team before it has evaluated implementation options.
Solution: State the behavior the customer needs. Keep technical choices in implementation planning unless a technical constraint is itself a requirement.
One criterion covers too many behaviors
Problem: A long sentence may combine validation, saving, confirmation, and error recovery. When it fails, the team may struggle to identify which behavior caused the problem.
Solution: Split the condition into smaller checks, such as one for valid submission and another for missing required fields.
Edge cases appear late
Problem: The team discovers an expired link or missing-permission case after implementation, creating avoidable rework.
Solution: During refinement, ask what happens when the action fails, the user lacks access, or the expected information is missing. Add only the consequential cases to the story.
FAQs about Jira acceptance criteria
Are acceptance criteria the same as a definition of done?
No. Acceptance criteria describe the conditions for a specific story, such as whether a password reset link expires after the agreed period. A definition of done is a shared quality bar that usually applies across many stories, such as completing review and testing. A team may use both: criteria confirm the story’s expected behavior, while the definition of done covers the team’s broader completion practices.
Who should write acceptance criteria in Jira?
The product owner or analyst may draft them, but the team should discuss and refine them together. Developers can flag technical or workflow questions, while testers can identify unclear outcomes and missing edge cases. A collaborative review helps people share the same understanding before work starts. The person who updates the Jira issue may vary by team, but the criteria should reflect a shared agreement.
How many acceptance criteria should a Jira story have?
There is no fixed number that fits every story. A small change might need two or three clear conditions, while a more involved workflow may need several. Keep the list focused on outcomes that matter and can be verified. If the criteria grow into unrelated behaviors or a large feature description, split the work into smaller stories or clarify the scope.
Can acceptance criteria change after a sprint begins?
They can change when the team learns something important or stakeholders revise the expected outcome. Discuss the change with the people responsible for scope, implementation, and testing, then update the Jira issue and assess its effect on the sprint. Quietly changing a criterion can leave teammates working to different expectations. Make the updated agreement visible to everyone involved.
Conclusion
Clear Jira acceptance criteria turn a story’s goal into outcomes your team can build and verify. Start with a reusable structure, describe observable behavior, and use examples to identify edge cases before sprint work begins.
The seven examples can help you shape criteria for common product flows, from sign-in to reporting. Keep each condition focused, review it with the team, and update the Jira issue when expectations change.
Vague criteria can lead to mismatched assumptions and late rework. A little shared clarification early makes completion easier to recognize and gives developers and testers a clearer path forward.