[wp-trac] [WordPress Trac] #49113: writing a bug report

[WordPress Trac]

#49113: writing a bug report
--------------------------+-----------------------------
 Reporter:  leezali5978   |      Owner:  (none)
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 The title should describe the problem as best as possible. Remember that
 the title is read more often than any other part of the bug report.

 Poor title: Notes don't display correctly
 This title is not specific enough for someone to look at it a month from
 now, and remember what the bug report is referring to.

 Good title: Stems too short for 32nd and 64th notes
 This title is an improvement over the previous title, because it specifies
 the type of notes that are affected and identifies the display problem.


 After submitting the issue, it is possible to improve the title.


 The first step in in writing a bug report is to identify exactly what the
 problem is. Saying "something is wrong" is not helpful; saying exactly
 what is wrong, and how to reproduce it, is. If you can tell exactly what
 is wrong, and reliably reproduce an example of the problem,
 like the one i had [https://thebestdishwasher2020.com/best-dishwasher-
 deals-2020/] broken links because of the bug.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/49113>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform