ERPWeb Odoo Upgrade Report

ERPWeb Test Client — Test Odoo 16 to 19 Upgrade — Odoo 16 to Odoo 19

Back to Project Work Packages Action Plan Risk Summary Dependency Summary Latest Scanner Findings Download HTML Report
CRITICAL Overall project risk
299 Risk score
17 Developer work packages
20.00 Open estimated hours

1. Executive Summary

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.

1 Uploaded modules
62 Scanner findings
0 Missing custom dependencies
0 / 17 Done work packages

2. Scanner Finding Breakdown

Critical: 0 High: 6 Medium: 30 Low: 6 Info: 20

3. Work Package Breakdown

To Do: 17 In Progress: 0 Blocked: 0 Review: 0 Done: 0 Deferred: 0

4. High-Risk Modules

critical Score: 299

erpweb_phase3_risky_test_module

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: 0

5. Missing Custom Dependencies

No missing custom dependencies detected.

6. Critical / High Scanner Findings

high python_api erpweb_phase3_risky_test_module

Old Odoo API method signature detected

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.

high python_api erpweb_phase3_risky_test_module

Old Odoo API method signature detected

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.

high python_api erpweb_phase3_risky_test_module

Old Odoo API method signature detected

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.

high python_api erpweb_phase3_risky_test_module

Old Odoo API method signature detected

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.

high python_api erpweb_phase3_risky_test_module

Old Odoo API method signature detected

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.

high python_api erpweb_phase3_risky_test_module

Old Odoo API method signature detected

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.

7. Developer Handover: Priority Work Packages

Critical To Do Module Review

Developer upgrade review: erpweb_phase3_risky_test_module

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:

Developer reviewed the source issue and confirmed the required upgrade action. Code changes, dependency changes, or notes are documented clearly. Updated module is re-uploaded or the finding is marked as not applicable with a reason. Scanner, dependency graph, and risk score are rebuilt after the change. Issue is tested in an upgraded Odoo target-version test environment before UAT.

Estimate: 6.00 hours

High To Do Scanner Finding

Old Odoo API method signature detected

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:

Developer reviewed the source issue and confirmed the required upgrade action. Code changes, dependency changes, or notes are documented clearly. Updated module is re-uploaded or the finding is marked as not applicable with a reason. Scanner, dependency graph, and risk score are rebuilt after the change. Issue is tested in an upgraded Odoo target-version test environment before UAT.

Estimate: 2.00 hours

8. Next 10 Open Work Packages

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

9. Recent Work Package Tracking History

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

Developer upgrade review: erpweb_phase3_risky_test_module

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

10. Delivery Recommendation

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.