Checkaroundme Feedback Board
Defects and product feedback from the Defects Log, #product-updates, GitLab and stand-ups. Close an item by marking its Linear issue Done; the board ticks itself within 15 minutes.
27to do
10urgent open
27with Thraize
3done
-
Enforce participant access when reading bookingsgetBookingById has no auth or ownership check. Test signed-out, unrelated user, customer, provider and admin.
-
Enforce actor roles for booking disputes and inspection pricingDispute branches and inspection set_booking_price don't check participant roles.
-
Build the notification map: one registry and notify() for every alertParent of NOTIF-1 to NOTIF-11. Mr. Afolabi approved the map on 28 Oct.
-
Tell providers about new direct booking requestsNotification gap 1
-
Send email/WhatsApp on every workflow job status changeNotification gap 2
-
Add notices for the 120-hour confirmation window and auto-completeNotification gap 3
-
Split "Booking Updated" into a message per eventNotification gap 4
-
Send expiry and payment-confirmed alerts through pushNotification gap 5
-
Notify every dispute step, with the outcome in the decision noticeNotification gap 6
-
Update refund notices to the new pricing rulesNotification gap 7
-
Apply consistent authentication controls and failure handlingPassword login skips the allowLogin check; a settings failure silently enables login/signup.
-
Prevent account deletion after OAuth profile lookup failuresA temporary profile lookup failure can delete an existing account when signup is disabled.
-
Route admin alerts to a team address, not one Gmail inboxNotification gap 8
-
Add rating prompt, payout-ready notice and reactivation messagesNotification gap 9
-
Let people choose their notification channelsNotification gap 10
-
Admin page to view the map and switch channels per pointNotification map build step
-
Customer has no wallet to receive a refund after cancelling a bookingMr. Afolabi's demo account; re-test with him
-
Technical assessment: commission, VAT, reconciliation, settlement and protected payments26 Oct action (was 'Azeez'); include Korapay
-
WhatsApp & Telegram bots, Phase 1: search, quote, book, pay, review in chatParent of BOT-1 to BOT-8 (Phase 1). After launch work; BOT-1 waits on Mr. Afolabi's approval, WhatsApp number and Meta budget.
-
Set up the WhatsApp Business number, Meta verification and Telegram botBOT-1. Blocked on Mr. Afolabi; Telegram bot can be made now for dev.
-
Shared conversation engine with WhatsApp and Telegram adaptersBOT-2
-
Link a chat to a Checkaroundme account with a one-time codeBOT-3
-
Search providers and show profile cards in chatBOT-4
-
Request and accept quotes in chatBOT-5
-
Book and pay through a checkout linkBOT-6
-
Confirm completion and collect a rating in chatBOT-7
-
Send outbound alerts through approved WhatsApp templatesBOT-8, sends through notify() (CAM-122)
-
Customer gets "Could not send request" when sending a service requestRaised in the 6 Nov stand-up from a customer screenshot. Thraize fixed it just before the call and the request now shows in the backend; not yet retested with the customer. Follow-ups: CAM-200, CAM-201, CAM-202.
-
Fix log out on mobile web: user stays signed in after logging outTried 3 times on mobile Chrome; avatar still shows after log out. Screenshot in Slack.
-
Simplify the wallet / payout / virtual account flow for non-tech-native providersRaised in the 3 Nov stand-up: many users are not native to technology, so wallets, payouts and virtual accounts may not work for them. Stephen is auditing the sign-up → wallet → bank payout flow.