Issue Triage Workflow

Stage 1: Preview

1. Sizes the description into categories: Tiny, Small, Medium, Large. See Description Sizes in references.md for size definitions.
2. Analyzes based on description size:
   • Tiny: Tries to detect what module is affected. Uses specific terms and method names. JDBC, for example, has very recognizable sets of methods. Remembers or outputs additional information.
   • Small or Medium: Finds what module or functionality is affected and records this information. Small or Medium descriptions just need more technical details.
   • Large: Refines and compacts the issue for further investigation. Large descriptions should have enough data to pinpoint the problem but are often in a form hardly readable by humans, so creates a minimal version.
3. Checks that there is minimal data available about the problem. See Minimal Issue Details in references.md.

Stage 2: Research

Before exploring the tree, use source-map.md to locate the affected module and area:* labels (module/package boundaries, label → source location, entry-point classes, and stacktrace → module heuristics). Only grep the source once the map has narrowed the scope.

Every issue type has its own research approach.