wagtail/.github/ISSUE_TEMPLATE/BUG_REPORT.md

---
name: '🐞 Bug Report'
about: Create a report to help us improve
title: ''
labels: ['type:Bug', 'status:Unconfirmed']
assignees: ''
---

<!--
Found a bug? Please fill out the sections below. 👍
-->

### Issue Summary

<!--
A summary of the issue.
-->

### Steps to Reproduce

1. (for example) Start a new project with `wagtail start myproject`
2. Edit models.py as follows...
3. ...

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?

-   I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: (yes / no)

### Technical details

-   Python version: Run `python --version`.
-   Django version: Look in your requirements.txt, or run `pip show django | grep Version`.
-   Wagtail version: Look at the bottom of the Settings menu in the Wagtail admin, or run `pip show wagtail | grep Version:`.
-   Browser version: You can use https://www.whatsmybrowser.org/ to find this out.
Add separate GitHub issue templates for feature requests and bugs. Fix #5560 (#5594) 2019-10-02 17:27:31 +02:00			`---`
auto-format core markdown files (#8603) - clean up formatting on existing martkdown files to align with prettier 2022-06-01 15:08:56 +02:00			`name: '🐞 Bug Report'`
Add separate GitHub issue templates for feature requests and bugs. Fix #5560 (#5594) 2019-10-02 17:27:31 +02:00			`about: Create a report to help us improve`
			`title: ''`
docs & github issue template - update bug issue triage (#8096) * update github bug template to have status:Unconfirmed - by default, ensure that all new bugs are raised with the label status:Unconfirmed - for the bug template where 'hints' exist - use HTML comments to hide these * docs - update issue tracking - convert from RST to markdown - add details about when to use Github discussions instead of an issue - add details about bugs will be raised with the status:Unconfirmed - add link to PR triage guide - add links to release schedule & roadmap - put less emphasis on milestones for new issue creation 2022-03-24 23:28:13 +01:00			`labels: ['type:Bug', 'status:Unconfirmed']`
Add separate GitHub issue templates for feature requests and bugs. Fix #5560 (#5594) 2019-10-02 17:27:31 +02:00			`assignees: ''`
			`---`

docs & github issue template - update bug issue triage (#8096) * update github bug template to have status:Unconfirmed - by default, ensure that all new bugs are raised with the label status:Unconfirmed - for the bug template where 'hints' exist - use HTML comments to hide these * docs - update issue tracking - convert from RST to markdown - add details about when to use Github discussions instead of an issue - add details about bugs will be raised with the status:Unconfirmed - add link to PR triage guide - add links to release schedule & roadmap - put less emphasis on milestones for new issue creation 2022-03-24 23:28:13 +01:00			`<!--`
Adds an Issue template and a Pull request template to Github 2016-09-08 12:03:16 +02:00			`Found a bug? Please fill out the sections below. 👍`
docs & github issue template - update bug issue triage (#8096) * update github bug template to have status:Unconfirmed - by default, ensure that all new bugs are raised with the label status:Unconfirmed - for the bug template where 'hints' exist - use HTML comments to hide these * docs - update issue tracking - convert from RST to markdown - add details about when to use Github discussions instead of an issue - add details about bugs will be raised with the status:Unconfirmed - add link to PR triage guide - add links to release schedule & roadmap - put less emphasis on milestones for new issue creation 2022-03-24 23:28:13 +01:00			`-->`
Adds an Issue template and a Pull request template to Github 2016-09-08 12:03:16 +02:00
			`### Issue Summary`

docs & github issue template - update bug issue triage (#8096) * update github bug template to have status:Unconfirmed - by default, ensure that all new bugs are raised with the label status:Unconfirmed - for the bug template where 'hints' exist - use HTML comments to hide these * docs - update issue tracking - convert from RST to markdown - add details about when to use Github discussions instead of an issue - add details about bugs will be raised with the status:Unconfirmed - add link to PR triage guide - add links to release schedule & roadmap - put less emphasis on milestones for new issue creation 2022-03-24 23:28:13 +01:00			`<!--`
Adds an Issue template and a Pull request template to Github 2016-09-08 12:03:16 +02:00			`A summary of the issue.`
docs & github issue template - update bug issue triage (#8096) * update github bug template to have status:Unconfirmed - by default, ensure that all new bugs are raised with the label status:Unconfirmed - for the bug template where 'hints' exist - use HTML comments to hide these * docs - update issue tracking - convert from RST to markdown - add details about when to use Github discussions instead of an issue - add details about bugs will be raised with the status:Unconfirmed - add link to PR triage guide - add links to release schedule & roadmap - put less emphasis on milestones for new issue creation 2022-03-24 23:28:13 +01:00			`-->`
Adds an Issue template and a Pull request template to Github 2016-09-08 12:03:16 +02:00
Ask issue openers to confirm that bugs are reproducible 2018-08-16 16:40:47 +02:00			`### Steps to Reproduce`
Clarify "Steps to reproduce" in new issue template (#3610) Bug reporters are frequently not making the connection that "Steps to reproduce" means "steps for someone else to independently reproduce this bug", not "steps that I go through on my project to see this bug". Added some example text to gently steer people towards the level of detail we want... Also trimmed down the "Wagtail version" item under "Technical details", since we don't really need to tell people four different ways to do the same thing. (We don't want people to mentally tune this text out, so I think it's a good habit to remove something for every new thing we add) 2017-05-30 21:31:23 +02:00
			1. (for example) Start a new project with `wagtail start myproject`
			`2. Edit models.py as follows...`
			`3. ...`
Adds an Issue template and a Pull request template to Github 2016-09-08 12:03:16 +02:00
Updated with feedback from Tom 2016-09-08 14:38:00 +02:00			`Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?`
Adds an Issue template and a Pull request template to Github 2016-09-08 12:03:16 +02:00
auto-format core markdown files (#8603) - clean up formatting on existing martkdown files to align with prettier 2022-06-01 15:08:56 +02:00			`- I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: (yes / no)`
Ask issue openers to confirm that bugs are reproducible 2018-08-16 16:40:47 +02:00
Adds an Issue template and a Pull request template to Github 2016-09-08 12:03:16 +02:00			`### Technical details`

auto-format core markdown files (#8603) - clean up formatting on existing martkdown files to align with prettier 2022-06-01 15:08:56 +02:00			- Python version: Run `python --version`.
			- Django version: Look in your requirements.txt, or run `pip show django \| grep Version`.
			- Wagtail version: Look at the bottom of the Settings menu in the Wagtail admin, or run `pip show wagtail \| grep Version:`.
			`- Browser version: You can use https://www.whatsmybrowser.org/ to find this out.`