Bugs

Reported by: Rhonda Haley QMS Version Number: Prod: 0.59.3 Prerequisites: (Facility Report) Rent Roll - NOTE: I exported this report and isolated the entries for Column G that have Cov. Prem. above $0.00 (Facility Report) Coverage Activity Steps to Produce: Step 1 – After isolating the entries for those with Cov. Prem. above $0.00, count the number of entries. Step 2 – Compare those entries against Covered in the Report: Coverage Activity Expected Result: The entries match. Actual Result: The entries do not match. Note: Rhonda reported this problem with Site: TS of Burbank Units: 562, 957, L149, L418, L443; Pricing details list no active coverage for these units. Other sites found impacted: TS of Commerce & TS of Portalnd 2 (checked 04/24); I cannot determine which exact units were impacted Site not impacted: TS of San Jose (checked 04/24) I cannot confirm this issue on QMS-Trial. Screenshots included

The site has informed us the tenant in units 562 and 2605, Briana Woerner made a payment on 4/14 to come out of overlock but Noke did not receive an update that the units were in an occupied/ in-use current status. The most recent updates Noke received for both units have the timestamp 2025-04-12 07:27:10UTC, with an overlock unit status for both. -QS Support did two full manual API syncs from QMS but Noke advised last sync for the tenants still shows as 2/12. Site: Trojan Storage - Campbell Tenant Name: Briana Woerner Linked Units: 562, 2605 Keycode: 6076801

See the screenshot. Sign button is hidden by the exit move-in button. Phone is Pixel 8 Pro running Android.

QMS provides Keycode configurations for Default Access Zones Group and Default Delinquency Behavior; however, based on documentation and my testing, these two parameters do not appear to do anything for the PTI Flat file integration. I have attached screenshots of settings found on QSC and QSX, which don't have these two fields and only allow you to specify the Access Level. Issue reported by Rhonda from Trojan Storage *I attached PTI Flat File Documentation

Reserve a Unit. Rent the Reserved Unit & notice the button label that should be Move-In is labeled Reserve.

PROD->BPDM Hermie and Sarah noted that they were able to create SMS numbers in the Admin app for Fredericksburg and Blue Ridge. However, it fails for Junction Hwy (see video below) https://www.loom.com/share/4d5682d5b0dc4209806bf717686cf2a3?sid=bf1ec9a5-cd43-4a64-ba01-51fd6f436627 I logged into our Production Twilio dashboard and it seems that there is no facility created for Junction Hwy. This is probably a bug where the Twilio facility did not get created when the facility was created in QMS. See the image.

Reported by: Matthew Keylon @ Stuff Safe Storage - Blueridge QMS Version Number: Prod: 0.59.3 Prerequisites: Tenant: Rolyn Casper M52: hannahjewlery@embarqmail.com (incorrect email) R11: hannahjewelry@embarqmail.com (correct email) Issue: I'm unable to update M52's email from < hannahjewlery@embarqmail.com > to < hannahjewelry@embarqmail.com > Attempts made: QMS->Facility->Tenant->Edit Tenant->Update email and save. Error: End user with that email already exists. QMS->Facility->Initiate transfer for Unit: M52 to Unit: P2->Updated Tenant Information and click Next Error: End user with that email already exists. This is one of the facility's end goals, but they are first trying to update the email.

Reported by: Rhonda Haley QMS Version Number: Prod & Trial: 0.59.3 Prerequisites: None Steps to Produce: Step 1 – Navigate to 'Start New SMS' pane and begin a SMS conversation with your desired client. Step 2 – Send out your message to the party. Step 3 – Refresh the page. Step 4 – Message will return result either queued with a grey dot, or sucessful with a green dot. Step 5 – Confirm you have recieved a message on your test phone or equivelant. It should be received regardeless of what result you get (grey or green) Expected Result: Successfully sent messages return with the green dot confirming it has been successfully sent. Actual Result: Sucessfully sent messages return with a queued message or sometimes with a green dot confirming it has been sent. It seems to be random and not based on factors such as: Hyperlink, length, if string is numerical, PNG images. Note: Tested in Trial QMS, in El Segundo. Ticket was tested in Live QMS, at glendale. Zendesk Ticket: https://quikstor.zendesk.com/agent/tickets/39243 Video: https://somup.com/cTfX1jsUo4

Reported by: Brian Kalpinski @ Menards Self Storage QMS Version Number: Prod & Trial: 0.59.3 Prerequisites: An existing Role&Permissions with: Lafayette Site Manager //this is the name of the role that the facility is using - Facility: All settings enabled. - Corporate: All disabled Steps to Produce: Step 1 – Create a new user and assign your role. Step 2 – Login. Step 3 – QMS->Facility->(left sidebar)Leads Expected Result: You can view Leads. Actual Result: You cannot view Leads. Note: In my testing, I found that the user can view Leads if you enable all permissions under Corporate. I found enabling every option for Leads only under Corporate does nothing.

Reported by: Facility & Rhonda Haley QMS Version Number: Prod & Trial: 0.59.3 Information on the issue: Move-in occurred in the morning ~02:45 PT //based on what was recorded on Elavon Elavon shows User Name: QSSWEB Card used: (Visa) x9124 | Exp Date: 05/27 I did some digging around, but I couldn't find anything within the QMS program related to this tenant other than they are now a Prospect Tenant. Screenshots attached for Elavon and CashApp (provided by tenant) This ticket is an investigation ticket that April requested to be opened.