This PR introduces a custom issue template for the project, designed to enhance the process of issue reporting and tracking. Here’s why the template is necessary and the key components included:
Why a Custom Issue Template is Necessary:
Consistency: Ensures a uniform structure for all reported issues, making it easier for contributors and maintainers to review and prioritize.
Clarity: Helps users articulate issues clearly, providing all essential information up front, reducing the need for follow-up questions.
Efficiency: Guides users through the reporting process, saving time on reviewing issues and streamlining workflows for both reporters and maintainers.
Prioritization: Based on the information in the template, this section assists in assessing the severity and urgency of issues.
Documentation: Acts as documentation to educate users on what makes an acceptable issue report.
Encouragement: Simplifies the reporting process, encouraging more contributions and engagement from the community.
Fixes: #328
Type of change
[x] New feature (non-breaking change that adds functionality)
[ ] Bug fix (non-breaking change that fixes an issue)
What does this PR do?
This PR introduces a custom issue template for the project, designed to enhance the process of issue reporting and tracking. Here’s why the template is necessary and the key components included:
Why a Custom Issue Template is Necessary:
Fixes: #328
Type of change
How should this be tested?
Mandatory Tasks
Please confirm the following: