Recording work and defects.
WHAT AN ISSUE SHOULD CONTAIN
What the problem or request is Why it matters
For a defect: what happened, what was expected, and how to reproduce it
WHY REPRODUCTION STEPS MATTER MOST
A defect that cannot be reproduced usually cannot be fixed.
WHAT TO INCLUDE FOR A DEFECT
Environment and version Exact error messages What was being done
WHAT LABELS PROVIDE
A way to filter and group.
WHAT TO AVOID
Dozens of labels nobody applies consistently Issues with no owner Issues open for years
WHAT TO DO WITH VERY OLD ISSUES
Close them, stating why.
WHY
A tracker full of things nobody will do conceals what matters.
WHAT TO LINK
Issues to the changes that address them.
WHY
So the reasoning is traceable from the code.
WHAT TO ESTABLISH
Who triages incoming issues, and how often.
WHAT TRIAGE DECIDES
Whether it is valid, what priority it has, and who owns it.
WHAT TO AVOID
A tracker used as a discussion forum.
