mature-analyze-ticket

Ticket triage analyzes incoming work items by verifying reported behavior, classifying outcomes, and assessing priority before development begins. It systematically reviews evidence, attempts reproduction, and records structured triage findings directly on the work item.

Duplicate detection during bug assessment checks existing discovery items to identify related work, links the tickets together, and recommends the correct next workflow for routing decisions. This prevents teams from building from unverified or redundant reports.

Classifying and documenting triage decisions involves recording findings, reproduction status, impact assessment, and recommended actions directly on work items. It updates frontmatter when appropriate and validates reported behavior before asserting any findings.

Ticket analysis applies to product management and support workflows involving discovery tickets, evidence review, and routing decisions. It requires structured triage records to accurately verify, classify, and prioritize bugs, requests, and incidents.

Verifying reported behavior before asserting findings ensures teams avoid building from unclear or unverified reports. The triage process requires validation of the reported issue through reproduction attempts and evidence review to confirm the bug exists.

Triaging incidents without structured triage records limits the ability to systematically verify behavior, classify outcomes, and document findings. The ticket analysis process depends on structured records and frontmatter updates to produce valid routing decisions and priority assessments.