Ticket templates

User story template with acceptance criteria

A user story describes a feature from the point of view of the person who needs it: who they are, what they want and why. Pair it with testable acceptance criteria and the team knows exactly when the ticket is done.

Generate one from your idea →

The template

**Title**:
[Tag] As a <role>, I want to <action> so that I can <benefit>

**Description**:
A brief story describing the feature from the user's perspective.

### Acceptance Criteria
- [ ] Clear outcome 1
- [ ] Clear outcome 2
- [ ] Clear outcome 3

### Technical Details
- Stack / tech used: ...
- Notes: ...

Example: from rough idea to ticket

What you type into KanBandit, and the ticket it turns into with this template.

Your input

users should be able to reset their password if they forget it, link via email, expires after an hour

Generated ticket

[Auth] As a registered user, I want to reset my password so that I can regain access to my account

Users who forget their password currently have to contact support. A self-service reset via an emailed, time-limited link lets them get back in on their own.

Acceptance Criteria

A "Forgot password?" link on the login page opens a form that asks for the account email
Submitting the form always shows the same confirmation message, whether or not the email exists
If the account exists, an email with a single-use reset link is sent within one minute
The link expires 60 minutes after it was sent; an expired link shows a clear message and a way to request a new one
After setting a new password the user is logged in and the link can no longer be used

Technical Details

Store only a hash of the reset token, together with its expiry
Rate-limit reset requests per email and per IP address
Invalidate existing sessions after a successful reset

Tips for better user stories

01Name a real role
"As a registered user" or "As an account admin" beats "As a user": it tells the team whose problem they are solving and which permissions apply.
02Keep the benefit
The "so that" part is what lets the team find a simpler solution. Without it, the story is just a task.
03Make every criterion testable
Each acceptance criterion should be checkable with a yes or no. "Fast" and "user-friendly" are not; "within one minute" is.
04Cover the unhappy paths
Expired links, wrong input and missing permissions are where most bugs hide. List them as criteria up front.
05Split stories that grow
If you need more than five or six criteria, the story probably holds two features. Split it so each one can ship on its own.

Other ticket templates

Turn your backlog notes into tickets like this

Write what you need in plain words. KanBandit fills in this template, including acceptance criteria, and syncs the ticket to Jira. Free to start.

Start free