SLA & Tasking Correction
Fixed SLA defaulting to 28 days across all orders
Problem
All order SLAs were defaulting to 28 days instead of using the configured SLA values. This was a critical issue affecting task timelines and reporting.
From the Chatlogs
Villar identified the issue immediately on go-live day (Feb 4, 11:33 AM):
"There is currently an issue with Order SLA, it has blanketed 28 days. This is for ordering and tasking. It should reflect what the SLAs are that is configured in the system for orders." The urgency was escalated multiple times:
"We NEED that piece for the SLAs NOW. Please deploy it. Do not wait." - Villar, Feb 4, 3:55 PM
Despite an initial fix attempt, Matt reported on Feb 7 that the issue persisted:
"The 28-day tasking timeframe is still occurring. You have previously confirmed that it was resolved but unfortunately it is still occurring."
Root Cause
The Order SLA field had no placeholder and was effectively preselecting the first SLA option (28 days).
Fix
Mark updated ProjectOrderType to make SLA optional with a blank default ("Choose an option"). He also sorted the SLA durations logically (5 → 10 → 28 days) and deployed to production on Feb 7.
"FIXED, DEPLOYED: Updated ProjectOrderType to make SLA optional + blank by default"
Impact
Restored correct task timelines and reporting accuracy across all ordering workflows.