Bug Hunt & Code Quality Live-Forever Ticket

### Dependency
- [x] Waiting for new bugs to be found

### Overview
The purpose of this live-forever ticket is for the assignee to document and propose fixes for bugs and code quality issues.

#### Details

The motivation for this ticket is for new devs to assign themselves and to find a bug (something that was clearly broken). This is meant to help the assignee build familiarity with the site, and for new devs to think about where to find it in the code.

### Action Items

#### Dev Assignee Action Items
- [ ] Assign yourself to this ticket
- [ ] Report a bug / code quality issue in the comment below (see Instructions for more info)
- [ ] Optionally propose an idea/ solution for the issue

#### PM/ Dev Lead Action Items
- [ ] If any Engineering tickets created from the comments below, list them here so we know that it has been addressed

### Resources/Instructions

#### Template

```
### Problem Description

### Proposed Solution

### Screenshots

Screenshot 1

Use this tag to specify width/height, or simply paste an image from the clipboard.

``

Status
| Ticket | In-Progress? | Completed? |
|--------|--------|--------|
| 🔴 | 🔴 | 🔴 |

```

#### Bug Reporting

- describe the issue at length, be specific about the conditions that reproduce the bug
- include pictures or videos if possible, document it using the `Details` dropdown on Github Issues
- note any relevant system info (e.g. operating system, browser, software version)

Example System Info

Desktop (please complete the following information):
OS: 13.3 (22E252)
Browser Chrome
Version 123.0.6312.86/87 / 26 March 2024

#### Code Quality Reporting

- describe the issue you have with the logic or implementation of the code
- provide the filename and which lines are affected by the quality issue
- provide links to resources that demonstrate a similar issue or provide insight on how to address the issue