Bug Hunt & Code Quality Live-Forever Ticket

[Skydodle]

Overview

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

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

**Report Type:** Bug reporting

**Describe the issue:**
<problem>

**Proposed Solution/ Ideas:**
<solution>

**Screenshots:**

<details>
<summary>Screenshot of Issue</summary>

Use this tag to specify width/height
<img src="" height="480px"/>

Or simply paste an image from the clipboard.

</details>

---

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

[ryanfchase]

@Skydodle I've added some more info to this ticket, but I'm happy to approve this. Thanks for getting this started!

[Skydodle]

Report Type: Bug reporting

Describe the issue: In the footer of the page where it says Powered by volunteers from Hack for LA, there should be a HFLA logo after it. I remembered it was there in previous versions, and it can also be seen in ALL of the current Figma designs. I think we might have accidentally removed the logo when we made changes to the footer.

Proposed Solution/ Ideas: The hack_for_la_logo.png already exist in the asset folder of the code base, we just need to add it back to the end of the text Powered by volunteers from Hack for LA in the footer.

ScreenShots:

Current footer missing HFLA logo

Proposed footer with HFLA logo

---

Status: Completed: https://github.com/hackforla/311-data/issues/1750

[ryanfchase]

Creating ticket for bug report:

• report comment: https://github.com/hackforla/311-data/issues/1726#issuecomment-2113969710
• new ticket: https://github.com/hackforla/311-data/issues/1750

[aqandrew]

Report Type: Bug reporting

Describe the issue: Misspelled property fontWieght is included in styles for AcknowledgeModal:

https://github.com/hackforla/311-data/blob/a16ce587e937e5b6a52579e6f8ebecc5e628c92e/components/Loading/AcknowledgeModal.jsx#L59

Proposed Solution/ Ideas: 400 is the default font weight in our typography settings. The screenshot below shows that font-weight: 400 has been set for this element already, despite the misspelled CSS property added by sx. Therefore the fontWieght entry can be safely removed from the object passed to the sx prop.

Screenshots:

DevTools showing misspelled CSS property

---

Status: Completed: https://github.com/hackforla/311-data/issues/1762

[ryanfchase]

Created ticket for bug report:

• New ticket: https://github.com/hackforla/311-data/issues/1762
• Referenced report: https://github.com/hackforla/311-data/issues/1726#issuecomment-2163764526

[ryanfchase]

Report Type: Bug reporting

Describe the issue: SR RequesetDetail loading spinner not appearing on subsequent mouse-over popups, causing stale info to be displayed before being refreshed with correct info

Proposed Solution/ Ideas: The loading spinner should appear above each SR while details are being loaded.

Screenshots:

Screenshot of Accessibility Modal

Status: Completed

• https://github.com/hackforla/311-data/issues/1805

[ryanfchase]

Report Type: Bug reporting

Describe the issue: Accessibility Modal cannot be dismissed by re-clicking on the Accessibility icon

Proposed Solution/ Ideas: Clicking on the icon should open and close the modal

Screenshots:

Screenshot of Accessibility Modal

---

Status: Completed

• https://github.com/hackforla/311-data/issues/1809

[ryanfchase]

Report Type: Bug reporting

Describe the issue: When selecting a date range from the Search & Filters modal, if you close the Datepicker dropdown AFTER picking an initial date, re-opening the menu does not restart your selection (aka there's no way to un-select your start date once you've picked one).

Proposed Solution/ Ideas: Closing the Datepicker should "reset" your selection, allowing you to start the selection over again

How to reproduce + Screenshots:

1. Click on datepicker to show dropdown
2. Click on a date
3. Click out of the datepicker dropdown, closing dropdown
4. Click on the datepicker, re-opening dropdown
5. Observe that the first date from Step 2 is still selected, user cannot undo this selection

Screen recording of Datepicker

---

Status

Ticket	In-Progress?	Completed?
🟡 #1836	🔴	🔴

[DrAcula27]

Report Type: Bug reporting

Describe the issue: When trying to deselect a NC, simply clicking outside the boundary of the selected NC does not deselect the selected NC. The user must click within the boundary of another NC to deselect the current one. This action also resets the map to the original zoom level, rather than selecting and zooming into the new NC.

Proposed Solution/Ideas:

• When deselecting the current NC by clicking into a new NC, the map should select and zoom into the new NC.
• When deselecting the current NC by clicking outside the boundary but not within another NC, the map should reset to its original zoom level.

Screenshots:

Screen recording of NC deselection

---

Status

Ticket	In-Progress?	Completed?
🟡 https://github.com/hackforla/311-data/issues/1837	🔴	🔴

[ryanfchase]

Report Type: Bug reporting

Describe the issue: When using the address search to find an address...

• if address is not within an NC, nothing happens
• console reports: {foundNcGeoObj: undefined}

Proposed Solution/ Ideas:

• [ ] Restore behavior prior to regression. Address search should always drop a pin, regardless if it is within an NC boundary
• [ ] Todo: open Emergent Request for design lead

Screenshots:

Screenshot of Issue

---

Status

Ticket	In-Progress?	Completed?
https://github.com/hackforla/311-data/issues/1840 🟡	🔴	🔴