How to write a great bug report

As someone who answers questions in the Community Support Forum, the following suggestions from the JetPack blog on how to write a bug report are also really excellent for helping us forum volunteers try to sort out any problem you may be experiencing with your blog. Sometimes, however, there may be a problem that only Support or Staff can help you with and, in that case, this is also the information you should send them when submitting a Support request.

Often bug reports don’t include enough information. Meaning we have go back and ask for details so we can investigate. If you want to increase the odds we fix an issue, and fix it fast, help us out.

A great bug report include the following:

  1. What were you trying to do?
  2. What did you click on or do last?
  3. What happened / what did you see?
  4. What browser are you using?
  5. What version of WordPress?  Not relevant for users, as we always have the most up-to-date version.
  6. What hosting provider? (And if you know, what version of PHP do they use?) Again, not relevant to users.

You don’t need to be verbose. A sentence for each is often just fine. And bug reports that show screenshots for #3 are incredibly useful, as we can see exactly what you saw.”

via How to write a great bug report — Jetpack.

Published by JenT

Empowered by WPcom since 2006. Never stop learning.

One thought on “How to write a great bug report

Comments are closed.