Documentation - how to write a bug ticket well

[TKDickson]

Documentation on how to fill out a bug ticket well, including things like:

• Required vs not required fields
• Context/why we do certain things
• Examples of well-filled out tickets
• FYI on the bug scrub process (so if you mess things up at least there's a backstop)
• Linking to said documentation from the internal bug ticket template

Will help make expectations around this clearer, for folks onboarding.

Credit to @brea11y for pointing out this was a good idea.

[DJUltraTom]

@TKDickson is the intent for this ticket to create a "How to" article, update the bug ticket template or both?
If a document/article is the desired output, where should this document live?

[TKDickson]

@DJUltraTom mostly a how-to article, but if you find that updating the ticket template along the way also makes sense, go for it. It should live on the QA section of the doc site, probably as a subpage of the Quality Assurance Process section.

[DJUltraTom]

Started working on a "how to article" in Github, and realized this needs more peer input than I'll be able to accomplish before EOD. moving this to "backlog" and after the "gap" this can be revisited.
A few points that can be emphasized are:

• Use the "Bug report Template"
• Specify the Require fields and Why.
• Screenshot examples for use from completed GH tickets (not the ZH tickets)
• Brief explanation of scrub process and ticket flow. (may change based on team structure)