Exercise 3: Why a Filled-In Template Isn't Automatically a Good Ticket — Possible Solution
====================================================================

WHAT THIS CHAPTER SAYS ABOUT TEMPLATES
------------------------------
Per this chapter, "a ticket template with required fields genuinely
helps make sure these core elements aren't forgotten - but a template
isn't satisfied just because every field has something typed into it."
A template's structure only guarantees that a placeholder exists for
each required element; it says nothing about the quality of what
actually gets written into that placeholder.

WHY A NON-EMPTY FIELD CAN STILL BE USELESS
------------------------------
Per this chapter, "a field filled with 'N/A' or a copy-pasted
non-answer defeats the entire point." Someone can technically comply
with a template's requirement (every field has some text in it) while
providing zero genuinely useful information - "N/A" in the "steps to
reproduce" field satisfies the form's own validation but tells whoever
picks up the ticket nothing at all.

WHAT ACTUALLY DETERMINES A GOOD TICKET
------------------------------
Per this chapter, "the goal is genuinely useful information in each
field, not merely a non-empty one." The measure isn't whether the
template's fields were completed, but whether the content in each
field actually provides the specific, checkable information this
chapter's own six-element list describes - an exact reproduction step,
a real timestamp, an actual correlation ID, and so on.

WHY THIS WORKS AS AN ANSWER
------------------------------
It distinguishes what a template's structure guarantees (a placeholder
exists) from what it can't guarantee (useful content in that
placeholder), and states the chapter's own actual standard - genuine
usefulness, not mere completion.