mirror of
https://github.com/Z3Prover/z3
synced 2026-05-23 02:19:37 +00:00
8e8799dbd3
This commit implements Phase 4 goals from the Daily Backlog Burner roadmap by adding structured issue templates to improve issue triage and quality. Added templates: - Bug Report: Comprehensive template for crash/correctness issues - Performance Issue: Specialized template for performance problems - Feature Request: Structured template for enhancement requests - Question: Template that guides users to appropriate channels - Build/Installation: Template for compilation and setup issues - Other: Catch-all template for miscellaneous issues - Config: Directs users to external resources (Discussions, Stack Overflow) Benefits: - Improves issue quality through structured reporting - Reduces maintainer time spent asking for missing information - Guides users to appropriate channels (Discussions vs Issues) - Enables better categorization and prioritization - Addresses identified patterns from backlog analysis These templates directly support the backlog management goals identified in issue #7903, helping transform the issue process from reactive to well-organized community engagement. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
65 lines
No EOL
2 KiB
YAML
65 lines
No EOL
2 KiB
YAML
name: 📋 Other Issue
|
|
description: For issues that don't fit other categories
|
|
title: "[Other] "
|
|
labels: []
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Please use this template only if your issue doesn't fit any of the other specific categories.
|
|
|
|
Consider whether your issue might be:
|
|
- **Bug Report** - Z3 crashes, gives wrong results, or behaves unexpectedly
|
|
- **Performance Issue** - Z3 is slower than expected or uses too much memory
|
|
- **Feature Request** - You need functionality that doesn't exist yet
|
|
- **Build/Installation** - Problems compiling or installing Z3
|
|
- **Question** - You need help understanding Z3's behavior
|
|
|
|
- type: dropdown
|
|
id: issue-category
|
|
attributes:
|
|
label: Issue Category
|
|
description: What type of issue is this?
|
|
options:
|
|
- Documentation problem
|
|
- Website/repository maintenance
|
|
- Security concern
|
|
- License question
|
|
- Community/governance
|
|
- CI/Testing infrastructure
|
|
- Release process
|
|
- Other (please specify)
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: description
|
|
attributes:
|
|
label: Description
|
|
description: Please describe your issue in detail
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: context
|
|
attributes:
|
|
label: Context
|
|
description: Additional context that might be helpful
|
|
placeholder: |
|
|
Related documentation:
|
|
Affected pages/sections:
|
|
Relevant links:
|
|
|
|
- type: textarea
|
|
id: proposed-solution
|
|
attributes:
|
|
label: Proposed Solution (if any)
|
|
description: If you have ideas on how to address this issue
|
|
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
### Before submitting
|
|
- [ ] I confirmed this doesn't fit other issue categories
|
|
- [ ] I searched for existing similar issues
|
|
- [ ] I provided sufficient detail for maintainers to understand the issue |