W16: Service Request Status Lifecycle (VERIFY)
Browsers: 2 (Worker, Manager)
Stories: SPRINT1-023
Status: 🔍 VERIFY (Database ready, UI needs updates)
Time: ~30 min
Test Items
- Service Request ID:
_________________ - Work Order ID:
_________________
Expected Lifecycle
pending → approved → processing → in_progress → fulfilled → closed
Automatic Transitions:
approved→processing(when WOs created)processing→in_progress(when WO assigned)in_progress→fulfilled(when all WOs completed)fulfilled→closed(auto after time or manual)
Test Cases
16.1: Verify Status Values Exist
Browser: Manager
Steps:
- Navigate to any service request detail page
- Check status field/display
- Document statuses visible:
-
pending,approved,processing,in_progress,fulfilled,closed,on-hold,cancelled -
convertedstill visible? (should be removed)
-
Verify: New statuses visible, converted removed
16.2: Automatic Transition - approved → processing
Browser: Manager
Steps:
- Find/create SR with status
approved - Record Service Request ID:
_________________ - Create work order from SR (unassigned)
- Refresh SR detail page
- Check status
Verify: Status = processing (or in_progress if WO assigned), automatic transition works
16.3: Automatic Transition - processing → in_progress
Browser: Manager
Steps:
- Use SR from 16.2 (status =
processing) - Assign work order to worker
- Refresh SR detail page
- Check status
Verify: Status = in_progress, automatic transition works
16.4: Automatic Transition - in_progress → fulfilled
Browser: Worker, Manager
Steps:
- Worker: Start and complete work order
- Manager: Refresh SR detail page
- Check status and completion badge
Verify: Status = fulfilled, completion badge shows (e.g., "1/1 ✓")
16.5: Completion Badge Display
Browser: Manager
Steps:
- Create SR with 3 work orders
- Complete 1 WO → verify badge "1/3"
- Complete 2nd WO → verify badge "2/3"
- Complete 3rd WO → verify badge "3/3 ✓"
Verify: Badge always visible, shows correct counts, updates correctly
16.6: Manual Close (fulfilled → closed)
Browser: Manager
Steps:
- Navigate to SR with status
fulfilled - Look for "Close Request" button
- Click button (if visible)
- Refresh SR detail page
- Check status
Verify: Button visible, status = closed, closed_at timestamp set
16.7: Re-Open Rule (fulfilled → in_progress)
Browser: Worker/Manager, Manager
Steps:
- Worker/Manager: Re-open completed work order (status →
in_progress) - Manager: Refresh SR detail page
- Check status
Verify: SR status reverts from fulfilled to in_progress
16.8: Partial Completion Rule (on_hold prevents fulfillment)
Browser: Worker, Manager
Steps:
- Create SR with 2 work orders
- Complete 1 WO
- Put other WO on hold
- Check SR status
- Resolve on_hold, complete WO
- Check SR status
Verify: SR remains in_progress with on_hold WO, transitions to fulfilled when resolved
16.9: Cancelled Work Orders Don't Count
Browser: Manager
Steps:
- Create SR with 3 work orders
- Cancel 1 WO
- Complete other 2 WOs
- Check SR status and completion badge
Verify: SR status = fulfilled, badge shows "2/2 ✓" (not "2/3")
16.10: Auto-Close Configuration
Browser: Manager/Admin
Steps:
- Navigate to Settings → System Settings
- Look for "Auto-close fulfilled requests after [X] hours"
- Change value, save
- Verify setting persists
Verify: Configuration exists, default 48 hours, can configure, setting persists
Findings
- Status: [ ] ✅ Complete [ ] ⚠️ Partial [ ] ❌ Blocked
- Database: [ ] ✅ Works [ ] ⚠️ Partial [ ] ❌ Broken
- UI: [ ] ✅ Works [ ] ⚠️ Partial [ ] ❌ Missing
- Notes:
_________________