As someone who frequently answers questions in the WordPress.com community support forums, the following suggestions from the JetPack blog on how to write a bug report are really excellent.
“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 includes the following:
- What were you trying to do?
- What did you click on or do last?
- What happened / what did you see?
- What browser are you using?
What version of WordPress?Not relevant for WordPress.com users, as we always have the most up-to-date version. What hosting provider? (And if you know, what version of PHP do they use?)Again, not relevant to WordPress.com 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.”