Knit Infotech Client workspace

What to Include in a Website or App Issue Report

A clear issue report helps the team reproduce the problem and ask fewer follow-up questions.

Include these details

  • The website address or app name, and the exact affected page or feature.
  • What you expected to happen and what actually happened.
  • Numbered steps that reproduce the issue.
  • The exact error message, with private information removed.
  • When it happened, including your timezone, and whether it happens every time.
  • Your browser or app version, device, and operating system.
  • Who is affected: one user, a group of users, or everyone.
  • Recent changes you know about, such as a deployment, plugin update, content change, or DNS change.

A useful report template

Affected URL/feature:
Expected result:
Actual result:
Steps to reproduce:
Time and timezone:
Device/browser:
Users affected and business impact:
Recent changes or workaround:

Attach a cropped screenshot when it helps. Remove passwords, API keys, one-time codes, payment details, and personal customer information. Describe what access is needed; ask the team for a suitable secure sharing method instead of posting credentials in a ticket.

Did you find this article useful?