Client: ERPWeb Test Client
Project: Test Odoo 16 to 19 Upgrade
Upgrade path: Odoo 16 → Odoo 19
Current stage: Dependency Review
Project status: Scanning
Risk summary: Project risk is CRITICAL with score 299. 1 module(s) scored. Highest-risk module: erpweb_phase3_risky_test_module (299).
Recommended next action: Treat this as a critical upgrade and assign senior developer review before UAT.
erpweb_phase3_risky_test_module is currently rated CRITICAL with score 299. 1 high scanner finding(s) found. 5 medium scanner finding(s) found.
Unique findings: 14 Critical: 0 High: 1 Missing deps: 0Location: erpweb_phase3_risky_test_module/models/risky_model.py:10
Description: This file appears to use the old cr, uid, ids, context method signature.
Suggested action: Convert old API methods to modern Odoo environment API using self.env and recordsets.
Location: erpweb_phase3_risky_test_module/models/risky_model.py:10
Description: This file appears to use the old cr, uid, ids, context method signature.
Suggested action: Convert old API methods to modern Odoo environment API using self.env and recordsets.
Location: erpweb_phase3_risky_test_module/models/risky_model.py:10
Description: This file appears to use the old cr, uid, ids, context method signature.
Suggested action: Convert old API methods to modern Odoo environment API using self.env and recordsets.
Location: erpweb_phase3_risky_test_module/models/risky_model.py:10
Description: This file appears to use the old cr, uid, ids, context method signature.
Suggested action: Convert old API methods to modern Odoo environment API using self.env and recordsets.
Location: erpweb_phase3_risky_test_module/models/risky_model.py:10
Description: This file appears to use the old cr, uid, ids, context method signature.
Suggested action: Convert old API methods to modern Odoo environment API using self.env and recordsets.
Location: erpweb_phase3_risky_test_module/models/risky_model.py:10
Description: This file appears to use the old cr, uid, ids, context method signature.
Suggested action: Convert old API methods to modern Odoo environment API using self.env and recordsets.
Summary: erpweb_phase3_risky_test_module is currently rated CRITICAL with score 299. 1 high scanner finding(s) found. 5 medium scanner finding(s) found.
Developer task: Start with this module first. Review all blockers, critical/high scanner findings, dependency issues, Phase 61 upgrade recommendations, API changes, XML/view migration risks, and JavaScript risks.
Acceptance criteria:
Estimate: 6.00 hours
Summary: This file appears to use the old cr, uid, ids, context method signature. Phase 61 recommendation: Convert old cr/uid/ids/context method signatures to modern self.env recordset-based API. Action category: convert_old_api_signature. Confidence: high. Review status: manual-review.
Developer task: Review scanner finding for erpweb_phase3_risky_test_module. Location: erpweb_phase3_risky_test_module/models/risky_model.py:10. Suggested action: Convert old API methods to modern Odoo environment API using self.env and recordsets. Use Phase 61 action category 'convert_old_api_signature' to group and sequence this work. Manual-review status: manual-review.
Acceptance criteria:
Estimate: 2.00 hours
| Priority | Status | Title | Assigned | Hours |
|---|---|---|---|---|
| Critical | To Do | Developer upgrade review: erpweb_phase3_risky_test_module | Unassigned | 6.00 |
| High | To Do | Old Odoo API method signature detected | Unassigned | 2.00 |
| Medium | To Do | Deprecated @api.multi usage | Unassigned | 2.00 |
| Medium | To Do | Legacy attrs usage detected | Unassigned | 2.00 |
| Medium | To Do | Legacy Odoo JavaScript module pattern detected | Unassigned | 2.00 |
| Medium | To Do | Legacy states usage detected | Unassigned | 2.00 |
| Medium | To Do | Legacy web.* JavaScript require detected | Unassigned | 2.00 |
| Low | To Do | Manifest version does not start with source Odoo major version | Unassigned | 1.00 |
| Info | To Do | Dependencies captured | Unassigned | 0.00 |
| Info | To Do | Dependencies detected | Unassigned | 0.00 |
Status: todo → todo · Assigned: phase71_test_developer → Unassigned · Hours: 6.00 → 6.00
Note: Phase 71 verification reset: restored assignment after tokened batch test BA-20260514120341005730.
2026-05-14 14:03
Status: todo → todo · Assigned: Unassigned → phase71_test_developer · Hours: 6.00 → 6.00
Note: Phase 71 bulk assignment batch: BA-20260514120341005730. Phase 71 status command positive assignment test.
2026-05-14 14:03
Status: todo → todo · Assigned: phase70_test_developer → Unassigned · Hours: 6.00 → 6.00
Note: Phase 70 verification reset: restored assigned developer after positive bulk assignment test.
2026-05-14 14:03
Status: todo → todo · Assigned: Unassigned → phase70_test_developer · Hours: 6.00 → 6.00
Note: Phase 70 verification assignment write and reset test.
2026-05-14 14:03
Status: todo → todo · Assigned: phase71_test_developer → Unassigned · Hours: 6.00 → 6.00
Note: Phase 71 verification reset: restored assignment after tokened batch test BA-20260514115434704832.
2026-05-14 13:54
Status: todo → todo · Assigned: Unassigned → phase71_test_developer · Hours: 6.00 → 6.00
Note: Phase 71 bulk assignment batch: BA-20260514115434704832. Phase 71 status command positive assignment test.
2026-05-14 13:54
Status: todo → todo · Assigned: phase70_test_developer → Unassigned · Hours: 6.00 → 6.00
Note: Phase 70 verification reset: restored assigned developer after positive bulk assignment test.
2026-05-14 13:54
Status: todo → todo · Assigned: Unassigned → phase70_test_developer · Hours: 6.00 → 6.00
Note: Phase 70 verification assignment write and reset test.
2026-05-14 13:54
Status: todo → todo · Assigned: phase71_test_developer → Unassigned · Hours: 6.00 → 6.00
Note: Phase 71 verification reset: restored assignment after tokened batch test BA-20260514114420898177.
2026-05-14 13:44
Status: todo → todo · Assigned: Unassigned → phase71_test_developer · Hours: 6.00 → 6.00
Note: Phase 71 bulk assignment batch: BA-20260514114420898177. Phase 71 status command positive assignment test.
2026-05-14 13:44
Status: todo → todo · Assigned: phase70_test_developer → Unassigned · Hours: 6.00 → 6.00
Note: Phase 70 verification reset: restored assigned developer after positive bulk assignment test.
2026-05-14 13:44
Status: todo → todo · Assigned: Unassigned → phase70_test_developer · Hours: 6.00 → 6.00
Note: Phase 70 verification assignment write and reset test.
2026-05-14 13:44
Status: todo → todo · Assigned: phase71_test_developer → Unassigned · Hours: 6.00 → 6.00
Note: Phase 71 verification reset: restored assignment after tokened batch test BA-20260514113951407443.
2026-05-14 13:39
Status: todo → todo · Assigned: Unassigned → phase71_test_developer · Hours: 6.00 → 6.00
Note: Phase 71 bulk assignment batch: BA-20260514113951407443. Phase 71 status command positive assignment test.
2026-05-14 13:39
Status: todo → todo · Assigned: phase70_test_developer → Unassigned · Hours: 6.00 → 6.00
Note: Phase 70 verification reset: restored assigned developer after positive bulk assignment test.
2026-05-14 13:39
Status: todo → todo · Assigned: Unassigned → phase70_test_developer · Hours: 6.00 → 6.00
Note: Phase 70 verification assignment write and reset test.
2026-05-14 13:39
Status: todo → todo · Assigned: phase71_test_developer → Unassigned · Hours: 6.00 → 6.00
Note: Phase 71 verification reset: restored assignment after tokened batch test BA-20260514113834907902.
2026-05-14 13:38
Status: todo → todo · Assigned: Unassigned → phase71_test_developer · Hours: 6.00 → 6.00
Note: Phase 71 bulk assignment batch: BA-20260514113834907902. Phase 71 status command positive assignment test.
2026-05-14 13:38
Status: todo → todo · Assigned: phase70_test_developer → Unassigned · Hours: 6.00 → 6.00
Note: Phase 70 verification reset: restored assigned developer after positive bulk assignment test.
2026-05-14 13:38
Status: todo → todo · Assigned: Unassigned → phase70_test_developer · Hours: 6.00 → 6.00
Note: Phase 70 verification assignment write and reset test.
2026-05-14 13:38
Treat this as a critical upgrade and assign senior developer review before UAT.
Recommended ERPWeb flow: assign the next open work packages, apply developer fixes, re-upload fixed module ZIPs, rerun extraction/scanning, rebuild dependencies, rebuild risk scores, rebuild work packages, then regenerate this report before client UAT.