---
name: Bug report
about: Create a report to help us improve
title: "[BUG]"
labels: bug
assignees: ''

---

**Describe the issue**
A clear and concise description of the issue you're facing.

**To Reproduce**
Steps to reproduce the behaviour:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

**Expected behaviour**
A clear and concise description of what you expected to happen.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**What team are you on?**
 Please provide the name of your team.

**Helpful links (Logs, Link to Build, Repo, PR etc.)** 
Please provide any helpful links for investigating the issue.

**Is there a Slack thread related to this bug?** 
After submitting this issue, you can use: @spy github issues create_comment repo=minitest-distributed issue_id=$NEW_ISSUE_ID on any relevant Slack threads to save that information here.

**Additional context**
Add any other context about the problem here.

If possible, assign appropriate severity level, priority (high, medium, low) and difficulty (easy, normal, difficult) labels to the issue.
SEV-1 <24-72h - Critical issue that actively impacts multiple users/products.
SEV-2 <14 days - Limited impact app or major inconvenience to app users, workarounds available.
SEV-3 <60 days - Minor issue requiring action, but not affecting a users ability to use the app.
SEV-4 <180 days - Minimal impact but something the team wants to fix eventually.
SEV-5 No timeline - Cosmetic issue or bugs, no effect on user's ability to use tooling.