BugIt articles | Taskivator

A bug report card with six labelled parts: title, steps to reproduce, expected, actual, environment and evidence.

A bug report template developers will actually read

A copyable bug report template, what each part is for, and the habits that turn a vague complaint into a ticket a developer can fix.

Read the article

BugIt4 min read

Catch duplicate bugs before you file them

Why one bug turns into several tickets, how to search a tracker so you find the earlier one, and what to do when you do.

Read the article

A decision path from checking the spec to three outcomes: bug, expected behavior or a gap in the spec.

BugIt3 min read

Is it a bug or expected behavior? How to check before you file

Before you file, check whether the behavior is a bug, a missing feature or intended. A short method using the spec, release notes, settings and the tracker.

Read the article

A row of example test runs, some passing and some failing, above a short table of what differed between the runs.

BugIt4 min read

How to report a bug that only happens sometimes

How to report an intermittent bug: count your runs, find what changes between them, and write the conditions down so a developer can chase it.

Read the article

BugIt5 min read

A bug that used to work: how to report a regression

How to report a regression: find the last version that worked, narrow the gap to the first one that failed, and give the developer a place to start.

Read the article

BugIt4 min read

Reproduce a bug from a log file: a detective's guide

How to find the failing moment in a log, trim it to what matters, turn it into repeatable steps and share it safely.

Read the article

An example screenshot frame with three callouts: show the address and build, crop to the problem, and cover personal data.

BugIt4 min read

Screenshots and recordings that help fix the bug

What to capture in a bug report screenshot or recording, how to crop and annotate it, and how to keep personal data and secrets out of the picture.

Read the article

Three steps from a customer complaint to a bug report: what was said, what you can repeat, and the report.

BugIt3 min read

Turn a customer complaint into a bug report engineers can act on

How support and QA can turn a vague customer complaint into a bug report: ask the right questions, separate what was seen from what was guessed, and protect personal data.

Read the article

A vague bug title next to a clear title that names the area, the symptom and the condition.

BugIt3 min read

How to write a bug title that gets triaged

A bug title is the one line most people read. Learn what to put in it, what to leave out, and how to test it against a tracker list before you file.

Read the article

All BugIt articles.

BugIt

A bug report template developers will actually read

Catch duplicate bugs before you file them

Is it a bug or expected behavior? How to check before you file

How to report a bug that only happens sometimes

A bug that used to work: how to report a regression

Reproduce a bug from a log file: a detective's guide

Screenshots and recordings that help fix the bug

Turn a customer complaint into a bug report engineers can act on

How to write a bug title that gets triaged