Why issue templates get filled in with "N/A"

Every team that has been burned by a one-line bug report reaches for the same fix: an issue template. Required fields, a checklist, maybe a dropdown. Two months later the tracker is full of issues where half the fields say "N/A" and the reproduction steps say "see title".

The template did not fail because people are lazy. It failed because it asks everybody the same questions regardless of what they came to say.

A form cannot know what you are reporting

A bug template asks for expected behaviour, actual behaviour, reproduction steps, environment and version. Now watch what happens when four different people meet it.

Someone reporting a crash fills in all five and the template has earned its keep. Someone requesting a feature has no actual behaviour, no reproduction steps and no version that matters, so they type "N/A" three times and feel slightly stupid. Someone reporting a design problem has no version either. Someone reporting a documentation error has nothing to reproduce because the software worked perfectly, it was the page that was wrong.

Three of the four learned that the form is mostly noise. And the lesson generalises: once a reporter has typed "N/A" into a required field, they have learned that fields are things you get past rather than things that matter. The next time they file a genuine crash, they will get past your reproduction steps field too.

Required fields train people to lie

Marking a field required does not produce an answer. It produces a answer. The person who does not have a version number types "latest". The person who cannot reproduce it types "happens sometimes". Both fields are now full, the form validates, and the ticket contains two statements that are worse than silence because they look like data.

An empty field is a question you can still ask. A field containing "latest" is a question everyone now believes has been answered.

This is the part that makes templates quietly expensive rather than merely ineffective. They do not just fail to collect information, they generate false confidence that the information was collected.

What templates are actually good at

They are good at exactly two things, and it is worth being clear-eyed about both.

Routing. Splitting incoming work into bug, feature request and question, so it lands in front of the right person with the right label. That works because the reporter genuinely does know which of those they are doing.

Setting a floor. A template says, in effect, "we expect a title and a paragraph, not a title". That is worth having even when nothing else in the form gets used.

What they are bad at is the thing they get bought for: extracting the specific missing detail from a specific report. That detail changes with every issue, and a form is by definition the same every time.

The alternative is a question, not a field

When a colleague files something vague and you happen to be standing next to them, you do not hand them a form. You ask one question, and it is usually the right one, because you read what they wrote first.

That is the difference. A template asks before reading. A person asks after. Everything a template does badly comes from being the wrong side of that line.

The obvious objection is that nobody has time to read every incoming issue and compose a tailored question, which is true, and is why the "just ask them" advice has never scaled past small teams. But the reading and the asking are mechanical enough to hand off. That is the entire premise of what we build: read this issue, ask the two or three things this report is missing, in the thread, while the reporter still has the failure in front of them.

If you keep the template, shrink it

Assuming you are not ready to change anything else, the cheapest improvement is subtraction:

• Make everything optional except the title. You lose nothing real and you stop manufacturing "N/A".
• Split by type before you ask anything. A bug form and a feature form that each ask three relevant questions beat one form asking eight.
• Cut every field you have never actually used to make a decision. Most teams have a version field they have not read in a year.
• Ask for one example, not a category. "Paste one time this happened" gets you further than "how often does this happen".

A short template that people fill in honestly is worth more than a thorough one they fill in to get past. That is a low bar, and most templates are under it.