Markup errors should point to the finding they are in

[artis3n]

Please fill out the Bug Form or Feature Request Below

---

Feature Request

I have some markup syntax errors in my report which only appear when I try to "Generate Report." This makes sense because that is when the whole thing tries to generate, however -

How am I supposed to identify the sections across all my findings with issues? The numbers on the left do not appear to correspond to the finding IDs in this report, so I have to manually crawl all of the text in all of the fields in all of the findings hoping I pick out where I did something wrong.

In my first pass through my findings, I found one bullet that was missing the closing -*, but I am still receiving these errors so there is something else.
Update: I found the second bullet missing a closing -*. There were only 2 lines with issues, that cascaded those errors in the screenshot. There's got to be a better way to debug those markup issues.

Example Use Case

As a user, I would like to expedite troubleshooting by following an error message directly to the finding causing the error.