Template preview
Configure your template and click Generate// create bug report & feature request templates in one click
Generate professional bug report and feature request templates for GitHub, GitLab, and internal trackers. Free, browser-based, no sign-up required.
Template preview
Configure your template and click GenerateSelect your target platform (GitHub, GitLab, Generic) and issue type (bug, feature, docs).
Add, remove, or reorder sections. Each section maps to a field in your template.
Click Generate, preview the result, then copy or download the file to your repo.
Issue templates standardize how contributors and users report bugs or request features. A well-structured template reduces back-and-forth, captures essential reproduction steps, and helps maintainers triage issues faster. This tool generates ready-to-use template files for GitHub (.github/ISSUE_TEMPLATE/), GitLab, or any tracker.
Place YAML templates in .github/ISSUE_TEMPLATE/your-template-name.yml. Markdown templates go in .github/ISSUE_TEMPLATE/your-template-name.md. GitHub auto-detects files in that folder and shows them when users open a new issue.
GitHub's YAML format (introduced 2021) creates structured forms with dropdowns, checkboxes, and validated fields. Markdown templates are simpler — users fill in a pre-filled text box. YAML forms are recommended for new projects as they enforce structure better.
Yes. Place multiple files in .github/ISSUE_TEMPLATE/ — GitHub shows a chooser screen when opening a new issue. You can have a bug report, feature request, and documentation template all active simultaneously.
GitLab reads Markdown templates from .gitlab/issue_templates/. Users select a template from a dropdown when creating a new issue. GitLab doesn't yet support the YAML structured form format that GitHub offers.
At minimum: a clear title, steps to reproduce, expected vs actual behavior, environment info (OS, browser, version), and severity. Optionally add a pre-submit checklist to ensure users searched for existing issues before filing.
Select "Generic / Internal" to get a clean Markdown template you can adapt for any tracker. While Jira and Linear have their own template systems, the Generic output gives you a solid structure to paste into their template editors.
An issue template is a pre-structured file that guides contributors and users when submitting bug reports, feature requests, or other issues in a project repository. Instead of receiving free-form, often incomplete reports, maintainers see consistent, well-organized submissions that include all the information needed to investigate and resolve the issue.
Issue templates are especially valuable in open-source projects where contributors may range from experienced developers to first-time users who are unfamiliar with what information is required. A clear template removes the guesswork and reduces the time spent asking follow-up questions.
💡 Looking for premium web development assets? MonsterONE offers unlimited downloads of templates, UI kits, and developer assets — worth checking out for your next project.
GitHub supports two formats for issue templates. The older Markdown format (.md) prefills a text editor with commented instructions and placeholder text. Users can edit freely, which gives flexibility but also means they might delete important sections.
The newer YAML format (.yml), introduced in 2021, creates interactive forms with labeled fields, dropdowns, checkboxes, and required validations. YAML forms are significantly better for data quality — users can't accidentally delete a field, and maintainers get consistently structured reports every time. This tool generates both formats so you can choose what fits your workflow.
A high-quality bug report template typically includes the following sections:
Feature request templates are structured differently from bug reports. Instead of reproduction steps, they focus on the problem being solved and the proposed solution:
GitLab uses Markdown templates stored in .gitlab/issue_templates/. When a user opens a new issue, they can choose a template from a dropdown at the top of the editor. GitLab also supports description templates for merge requests via .gitlab/merge_request_templates/.
Unlike GitHub's YAML forms, GitLab templates are always Markdown — users still edit free text, but the prefilled structure guides them toward completeness. The generated output from this tool is fully compatible with GitLab's format.
A few principles that make templates more effective in practice:
required: true on steps-to-reproduce and environment fields — these are almost always essential.bug or feature-request in the template metadata so issues are pre-categorized on submission.CONTRIBUTING.md so reporters can understand your project's norms before submitting.After generating your template with this tool, add it to your repository by following these steps:
.github/ISSUE_TEMPLATE/ directory in your repository root if it doesn't already exist.bug_report.yml or feature_request.yml.config.yml in the same folder to add a "blank issue" link or external links (e.g. linking to your forum or security policy for vulnerability reports).Once deployed, users who click "New Issue" in your repository will see a template chooser instead of a blank editor — improving report quality from day one.