Ask HN: Resources on describing bugs to engineering teams

I'm currently a PM at a small startup. We have a 20 person engineering team that works in a separate office from the business team (sales, product, etc).

I manage a team of 2 product analysts who help with QA, booking bug tickets, and documenting user stories.

The analysts are fairly new to working with engineers, and are having trouble clearly communicating with them. Specifically, they struggle with booking bug tickets. I find that they don't have an intuitive sense of a few things:

1. How to investigate an issue prior to reporting it to the engineers 2. Which details to include in the description to make things easier on the engineer 3. Which things to EXCLUDE that are confusing or potential red herrings

...etc

My goal is to write up a training doc that will get the stuff out of my head and into theirs. However, I'm sure there are already good resources on this topic. Does anyone have suggestions of where to start?