Release 3.1Metrics
Day-by-Day Timeline
Detailed activity timeline extracted from Slack communications
Tuesday, 4 February - Go-Live Day
Key Events:
- Ordering system pointed to production (Mark, 4:23 AM)
- Service line items found missing - immediate call initiated
- SLA bug discovered - all orders defaulting to 28 days
- Metricon company access enabled for staff
- Missing and duplicate notification issues reported
- Invoice line items (118, 119) added to production
- EmailTemplate records synced from preprod to production
Tone: High urgency. Villar escalated SLA fix with @here and "do not wait" directives.
Wednesday, 5 February - File Upload & Configuration
Key Events:
- File upload 403/413 errors reported by multiple users (Jake, Ashleigh, Hannah)
- Root cause identified: file size limit on server configuration
- Villar updated server config - resolved within 30 minutes of root cause ID
- Permit Apply category misalignment identified (Document vs Building Permit)
- Map display missing on production - Mark had forgotten to enable config
- Notification content discrepancies identified between environments
- Day-one user feedback received from LG users (3 priority issues)
- Order notes persistence bug identified (Save & Continue wiping notes)
Tone: Reactive but methodical. Multiple parallel investigation threads.
Thursday, 6 February - Release 3.1 Deploy
Key Events:
- Release 3.1 items confirmed and listed (10 items)
- Releases 3.0 and 3.1 deployed together
- Commence Ordering confusion resolved (Ordering Portal vs Customer Portal behaviour)
- Villar corrected Mark's "old/new" portal framing
- Jayrex completed UAT sync for continued testing
- Mark confirmed Permit Apply category change to Building Permit
- Jayrex deployed fixes #1 and #3 from user feedback to preprod
Notable exchange:
"Old? No dude. Stop. Wait. ORDERING Portal is Ordering Portal. CUSTOMER Portal is Customer Portal. Both are current. None are old or new." - Villar, correcting Mark's terminology
Friday, 7 February - Peak Incident Day
Key Events:
- Dashboard v2 access changes deployed by Villar
- Document upload modal bug reported (3+ documents breaking UI)
- Email notification links misdirecting Metricon users
- Management Dashboard exposure check requested
- 28-day SLA still occurring despite previous "fix" confirmation
- 403 errors across all FTS users
- Dashboard v2 URL routing fix deployed by Mark
- SLA fix redeployed (optional + blank default)
- Ordering access issues for Royston users
- Multiple simultaneous production fires
Peak pressure point: 5+ concurrent production issues being triaged and fixed simultaneously.
"Smooth as a cactus Mark, but you stuck the landing regardless. Well done."
Saturday, 8 February - Access & Resubmit
Key Events:
- Unauthorised ordering access - Royston user Lee ordering without access
- Resubmit button visibility issue raised (clients changing order status)
- Jayrex tightened access enforcement across login, API, and active sessions
- Mark hid Resubmit button for rejected orders
- Dynamic email notification link routing implemented
- Manage Delays fix confirmed for original project but not platform-wide
- Jayrex deployed deep fix for resubmission logic
- Matt requested project deletion for erroneously created project
Monday, 10 February - Notification & Rejection Fixes
Key Events:
- Villar reported missing notifications for Metricon jobs (raised as Trello bug)
- Rejection reason codes not appearing - Villar found while processing a DA rejection
- Jayrex fixed: outdated script referencing deprecated field
- Jayrex deployed order notes sync fix to production
- Matt at 2-day conference - limited availability
Tuesday, 11 February - BP Status & LSIO
Key Events:
- BP status dating fix - separating project status triggers from order workflow
- LSIO and BAL datapoints rolled out to production
- VicMap/Pozi mapping layer research discussed
- Jayrex confirmed no scheduled release this week (team focused on patches)
- Villar confirmed next release scheduled for following week
- Matt identified project order attachment error
Tone: Stabilisation winding down. Forward-looking discussions beginning.