meta: Restructure Bug Report Issue Template #1852
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change separates the GitHub Bug Report Issue template's Expected/Actual Result section into two separate sections titled Expected Result and Actual Result. This change should make it easier to tell at a quick glance what the user expected to happen versus what actually happened, and it will hopefully make bug report issues easier for us to understand. We already have separate expected and actual results sections in the getsentry/sentry-python repository, and I find issues with the separated structure easier to read and understand.