Bug Tracker Practice
Write bug tickets like a pro. Fill out the form, then compare your report against a model answer.
Create a Ticket
Imagine you found a bug while testing. Fill out every field as if a developer you have never met will read it tomorrow.
Model Answer Comparison
Not sure how your ticket stacks up? Reveal a model answer for the bug “Login button fails on mobile Safari” and see what makes each field strong.
Login button unresponsive on iOS Safari — users cannot authenticate
Why it works: Specific, not vague. Names the feature, the platform, and the user impact. A developer knows immediately where to look.
High / Major
Why it works: Priority reflects business impact (users blocked from core flow). Severity reflects technical impact (a major feature is broken, but there is a workaround via desktop).
Safari 17.1, iOS 17.1.1, iPhone 14 Pro, staging environment (https://staging.example.co.nz), logged in as test user QA-001
Why it works: Exact browser version, device, URL, and account. A developer can reproduce this in 60 seconds without asking follow-up questions.
1. Open Safari on iPhone 14 Pro (iOS 17.1.1)
2. Navigate to https://staging.example.co.nz/login
3. Enter valid credentials (QA-001 / TestPass123!)
4. Tap the blue “Log In” button
Why it works: Numbered, exact, and copy-pastable. Includes test credentials so the developer does not need to hunt for them.
User is redirected to the account dashboard and the session cookie is set.
Why it works: Describes the success state clearly. “Redirected to dashboard” is measurable.
Nothing happens. The button shows a brief tap highlight but no network request is fired (confirmed via Safari remote inspector). No error message is shown.
Why it works: Clear contrast with expected. Notes the absence of an error message (a secondary bug) and confirms with tooling (remote inspector).
Common Jira Mistakes
❌ Vague summary
A vague summary forces the reader to open the ticket to understand what is wrong.
✅ Good summary
❌ Missing environment
Without environment details, the bug may be impossible to reproduce.
✅ Specific environment
❌ No steps to reproduce
Developers should not need to guess how you triggered the bug.
✅ Numbered steps