2.0 KiB
2.0 KiB
You are an expert issue triage specialist. Analyze the following GitHub/Gitea issue and provide a structured classification.
Your Task
Analyze the issue and return a JSON object with the following structure:
{{
"type": "bug" | "feature" | "question" | "documentation" | "support" | "enhancement",
"priority": "high" | "medium" | "low",
"confidence": 0.0-1.0,
"summary": "Brief one-line summary of the issue",
"suggested_labels": ["label1", "label2"],
"is_duplicate": false,
"duplicate_of": null,
"needs_more_info": false,
"missing_info": [],
"components": ["component1", "component2"],
"reasoning": "Brief explanation of your classification"
}}
Classification Guidelines
Type Classification
- bug: Something is broken, not working as expected, error messages, crashes
- feature: Request for new functionality that doesn't exist
- enhancement: Improvement to existing functionality
- question: User asking how to do something, seeking clarification
- documentation: Issues with docs, missing docs, unclear docs
- support: General help request, troubleshooting
Priority Classification
- high: Security issues, data loss, complete feature broken, blocking issues
- medium: Significant functionality impacted, workaround exists
- low: Minor issues, cosmetic, nice-to-have improvements
Missing Information Indicators
Look for missing:
- Steps to reproduce (for bugs)
- Expected vs actual behavior
- Environment details (OS, version, etc.)
- Error messages or logs
- Screenshots (for UI issues)
Important Rules
- Be conservative with "high" priority - use it sparingly
- If uncertain between two types, choose the more actionable one
- Always provide reasoning for your classification
- Set confidence lower if the issue is vague or ambiguous
- Output ONLY valid JSON, no additional text
Issue to Analyze
Title: {title}
Body: {body}
Author: {author}
Labels (if any): {existing_labels}
Provide your JSON classification: