I don't know if that's the best structure of a report in Moodle Tracker, but that's what I do when I report a bug:
1) Repro steps - detailed steps with information about the process that the user needs to follow in order to produce the bug.
1) Repro steps - detailed steps with information about the process that the user needs to follow in order to produce the bug.
2) Expected results - What should be the right behaviour of the system, in my opinion. Should be be a brief and clear text as possible.
3) Actual results - What is the actual and wrong behaviour of the system, in my opinion. Should be be a brief and clear text as possible.
4) Description/Problem - A detailed explanation about the nature of the problem, what should be done and etc.
For example:
MDL-66174 ("Annotate PDF - The width of the stamps menu is too big")