Recommendation-to-Developer Execution View

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

Developer Work Packages grouped into a recommendation-to-developer execution view.

Back to Project Upgrade Recommendations Upgrade Report Export Evidence CSV Action Plan Risk Summary Dependency Summary Latest Scanner Findings Projects Dashboard
Developer flow: fix work in sequence order, starting with blocker/critical/high and manual-review items. Auto-safe dependency items can usually be confirmed later, but still need evidence before being marked complete.

Developer Work Package Closure Readiness Dashboard

Project-lead view of which work packages are not ready to close, why they are not ready, and what action/evidence is still missing. This is calculated from existing work package fields and tracking history.

17 Total packages assessed
17 Not ready to close
0 Ready to close
0 Already closed
17 Missing developer assignment
15 Missing/weak evidence
2 High-impact not ready
0 Blocked packages

Top Not-Ready Closure Items

Package Priority Status Readiness Why not ready Missing action/evidence
#15 — Developer upgrade review: erpweb_phase3_risky_test_module Critical To Do Not Ready
  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • High-impact package is not yet in Review.
  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
#1 — Old Odoo API method signature detected High To Do Not Ready
  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • High-impact package is not yet in Review.
  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
#10 — Legacy Odoo JavaScript module pattern detected Medium To Do Not Ready
  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.
  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
#11 — Legacy web.* JavaScript require detected Medium To Do Not Ready
  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.
  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
#12 — Deprecated @api.multi usage Medium To Do Not Ready
  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.
  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
#14 — Legacy attrs usage detected Medium To Do Not Ready
  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.
  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
#13 — Legacy states usage detected Medium To Do Not Ready
  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.
  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
#9 — Manifest version does not start with source Odoo major version Low To Do Not Ready
  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.
  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
#2 — Dependencies captured Info To Do Not Ready
  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.
  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
#3 — Structured dependency records rebuilt Info To Do Not Ready
  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.
  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
17 Total work packages

Next: #15 — Developer upgrade review: erpweb_phase3_risky_test_module

17 Open execution items
15 Manual-review open items
2 Auto-safe open items
20.00 Estimated developer hours
1 Critical
1 High
0 Blockers

Status Breakdown

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

Package Type Breakdown

Blocker: 0 Module Review: 1 Scanner Finding: 14 Dependency: 2

Fix First Queue

These are the first items a developer should look at, sorted by upgrade sequence, priority, module, and recommendation category.

Seq Priority Module Action Category Review Work Package Status
20 Critical erpweb_phase3_risky_test_module Score 299 Manual Review #15 — Developer upgrade review: erpweb_phase3_risky_test_module To Do
32 High erpweb_phase3_risky_test_module Convert Old API Signatures Manual Review #1 — Old Odoo API method signature detected To Do
42 Medium erpweb_phase3_risky_test_module Migrate Legacy JavaScript Module Pattern Manual Review #10 — Legacy Odoo JavaScript module pattern detected To Do
42 Medium erpweb_phase3_risky_test_module Migrate Legacy web.* JavaScript Imports Manual Review #11 — Legacy web.* JavaScript require detected To Do
42 Medium erpweb_phase3_risky_test_module Modernize Recordset API Manual Review #12 — Deprecated @api.multi usage To Do
42 Medium erpweb_phase3_risky_test_module Review / Convert attrs Modifiers Manual Review #14 — Legacy attrs usage detected To Do
42 Medium erpweb_phase3_risky_test_module Review / Convert states Modifiers Manual Review #13 — Legacy states usage detected To Do
52 Low erpweb_phase3_risky_test_module Update Manifest Version for Target Manual Review #9 — Manifest version does not start with source Odoo major version To Do
62 Info erpweb_phase3_risky_test_module Dependency Review Manual Review #2 — Dependencies captured To Do
62 Info erpweb_phase3_risky_test_module Dependency Review Manual Review #3 — Structured dependency records rebuilt To Do
62 Info erpweb_phase3_risky_test_module Dependency Review Manual Review #4 — Dependencies detected To Do
62 Info erpweb_phase3_risky_test_module Dependency Review Manual Review #5 — Dependencies detected To Do

Execution by Module

Use this section when assigning a developer to a specific module. Each module shows the highest-impact work first.

erpweb_phase3_risky_test_module

Total: 17 Open: 17 Manual-review: 15 Auto-safe: 2 Critical/High: 2 20.00h
Seq 20 Critical Module Review To Do 6.00h erpweb_phase3_risky_test_module Score 299 Manual Review Not Ready

#15 — Developer upgrade review: erpweb_phase3_risky_test_module

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • High-impact package is not yet in Review.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
  • Prioritise review evidence before lower-risk closure work.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

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 / evidence required:

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.
Latest completion evidence: Phase 65 verification evidence: completion gate accepts Done only when evidence is captured. · May 14, 2026, 12:36 p.m. · Phase65 Verification Developer

Latest tracking history

Status: done → todo · Assigned: Phase65 Verification Developer → - · Hours: 6.00 → 6.00
Evidence / change note: Phase 65 verification reset: returned package to To Do after positive evidence test.
May 14, 2026, 12:36 p.m.
Status: todo → done · Assigned: - → Phase65 Verification Developer · Hours: 6.00 → 6.00
Evidence / change note: Phase 65 verification evidence: completion gate accepts Done only when evidence is captured.
May 14, 2026, 12:36 p.m. · Changed by Phase65 Verification Developer
Status: review → todo · Assigned: Phase9 Test Developer → - · Hours: 6.50 → 6.00
Evidence / change note: Reset after Phase 9 verification
May 11, 2026, 4:20 p.m.

Source: Risk scoring / score 299

Trace key: module-risk:1:critical:299

Open module

Seq 32 High Scanner Finding To Do 2.00h erpweb_phase3_risky_test_module Convert Old API Signatures Manual Review Not Ready

#1 — Old Odoo API method signature detected

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • High-impact package is not yet in Review.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
  • Prioritise review evidence before lower-risk closure work.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

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 / evidence required:

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.
Latest completion evidence: Fixed old API method signature, verified on staging build, scanner report rebuilt and evidence captured in commit abc123. · May 14, 2026, 1:10 p.m.
Latest completion evidence: Fixed old API method signature, verified on staging build, scanner report rebuilt and evidence captured in commit abc123. · May 14, 2026, 1:06 p.m.
Latest completion evidence: Fixed old API method signature, verified on staging build, scanner report rebuilt and evidence captured in commit abc123. · May 14, 2026, 1:05 p.m.
Latest completion evidence: Fixed old API method signature, verified on staging build, scanner report rebuilt and evidence captured in commit abc123. · May 14, 2026, 1:01 p.m.
Latest completion evidence: Fixed old API method signature, verified on staging build, scanner report rebuilt and evidence captured in commit abc123. · May 14, 2026, 1:01 p.m.
Latest completion evidence: Fixed old API method signature, verified on staging build, scanner report rebuilt and evidence captured in commit abc123. · May 14, 2026, 1:01 p.m.
Latest completion evidence: Fixed old API method signature, verified on staging build, scanner report rebuilt and evidence captured in commit abc123. · May 14, 2026, 1 p.m.
Latest completion evidence: Fixed old API method signature, verified on staging build, scanner report rebuilt and evidence captured in commit abc123. · May 14, 2026, 12:59 p.m.
Latest completion evidence: ok · May 14, 2026, 12:56 p.m.

Latest tracking history

Status: done → todo · Assigned: - → - · Hours: 2.00 → 2.00
Evidence / change note: Phase 67 verification reset: restored package after positive quality-gate test.
May 14, 2026, 1:10 p.m. · Changed by phase67_status
Status: todo → done · Assigned: - → - · Hours: 2.00 → 2.00
Evidence / change note: Fixed old API method signature, verified on staging build, scanner report rebuilt and evidence captured in commit abc123.
May 14, 2026, 1:10 p.m.
Status: done → todo · Assigned: - → - · Hours: 2.00 → 2.00
Evidence / change note: Phase 67 verification reset: restored package after positive quality-gate test.
May 14, 2026, 1:06 p.m. · Changed by phase67_status

Source: Phase 61 scanner recommendation / convert_old_api_signature

Trace key: scanner:erpweb_phase3_risky_test_module|python_api|Old Odoo API method signature detected|erpweb_phase3_risky_test_module/models/risky_model.py|10

Open module · Open scan source

Seq 42 Medium Scanner Finding To Do 2.00h erpweb_phase3_risky_test_module Migrate Legacy JavaScript Module Pattern Manual Review Not Ready

#10 — Legacy Odoo JavaScript module pattern detected

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
  • Add a meaningful evidence note: what changed, where it was tested, and proof/reference.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

Summary: This JavaScript file uses odoo.define, which may need migration for newer Odoo frontend architecture. Phase 61 recommendation: Review legacy odoo.define JavaScript and migrate it where required for the target Odoo frontend architecture. Action category: migrate_legacy_javascript_module. Confidence: medium. Review status: manual-review.

Developer task: Review scanner finding for erpweb_phase3_risky_test_module. Location: erpweb_phase3_risky_test_module/static/src/js/risky.js:1. Suggested action: Review whether this should be converted to the modern Odoo JavaScript module format. Use Phase 61 action category 'migrate_legacy_javascript_module' to group and sequence this work. Manual-review status: manual-review.

Acceptance criteria / evidence required:

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.

Source: Phase 61 scanner recommendation / migrate_legacy_javascript_module

Trace key: scanner:erpweb_phase3_risky_test_module|javascript|Legacy Odoo JavaScript module pattern detected|erpweb_phase3_risky_test_module/static/src/js/risky.js|1

Open module · Open scan source

Seq 42 Medium Scanner Finding To Do 2.00h erpweb_phase3_risky_test_module Migrate Legacy web.* JavaScript Imports Manual Review Not Ready

#11 — Legacy web.* JavaScript require detected

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
  • Add a meaningful evidence note: what changed, where it was tested, and proof/reference.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

Summary: This JavaScript file imports old web.* modules, which often change between Odoo versions. Phase 61 recommendation: Review legacy web.* JavaScript imports and migrate them to the target Odoo frontend service/module patterns. Action category: migrate_legacy_web_js_imports. Confidence: medium. Review status: manual-review.

Developer task: Review scanner finding for erpweb_phase3_risky_test_module. Location: erpweb_phase3_risky_test_module/static/src/js/risky.js:3. Suggested action: Review frontend imports and services against the target Odoo version. Use Phase 61 action category 'migrate_legacy_web_js_imports' to group and sequence this work. Manual-review status: manual-review.

Acceptance criteria / evidence required:

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.

Source: Phase 61 scanner recommendation / migrate_legacy_web_js_imports

Trace key: scanner:erpweb_phase3_risky_test_module|javascript|Legacy web.* JavaScript require detected|erpweb_phase3_risky_test_module/static/src/js/risky.js|3

Open module · Open scan source

Seq 42 Medium Scanner Finding To Do 2.00h erpweb_phase3_risky_test_module Modernize Recordset API Manual Review Not Ready

#12 — Deprecated @api.multi usage

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
  • Add a meaningful evidence note: what changed, where it was tested, and proof/reference.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

Summary: This file uses @api.multi, which is deprecated/removed in newer Odoo versions. Phase 61 recommendation: Remove/replace @api.multi usage and verify the method behaves correctly with modern Odoo recordsets. Action category: modernize_recordset_api. 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:6. Suggested action: Review and convert the method to modern recordset-style API for the target Odoo version. Use Phase 61 action category 'modernize_recordset_api' to group and sequence this work. Manual-review status: manual-review.

Acceptance criteria / evidence required:

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.

Source: Phase 61 scanner recommendation / modernize_recordset_api

Trace key: scanner:erpweb_phase3_risky_test_module|python_api|Deprecated @api.multi usage|erpweb_phase3_risky_test_module/models/risky_model.py|6

Open module · Open scan source

Seq 42 Medium Scanner Finding To Do 2.00h erpweb_phase3_risky_test_module Review / Convert attrs Modifiers Manual Review Not Ready

#14 — Legacy attrs usage detected

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
  • Add a meaningful evidence note: what changed, where it was tested, and proof/reference.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

Summary: This XML file uses attrs. In newer Odoo versions, view modifier handling may need review. Phase 61 recommendation: Review attrs-based view modifiers and convert where required for the target Odoo view syntax. Action category: review_convert_attrs_modifiers. Confidence: medium. Review status: manual-review.

Developer task: Review scanner finding for erpweb_phase3_risky_test_module. Location: erpweb_phase3_risky_test_module/views/risky_views.xml:5. Suggested action: Review this view against the target Odoo version's XML/view modifier requirements. Use Phase 61 action category 'review_convert_attrs_modifiers' to group and sequence this work. Manual-review status: manual-review.

Acceptance criteria / evidence required:

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.

Source: Phase 61 scanner recommendation / review_convert_attrs_modifiers

Trace key: scanner:erpweb_phase3_risky_test_module|xml_views|Legacy attrs usage detected|erpweb_phase3_risky_test_module/views/risky_views.xml|5

Open module · Open scan source

Seq 42 Medium Scanner Finding To Do 2.00h erpweb_phase3_risky_test_module Review / Convert states Modifiers Manual Review Not Ready

#13 — Legacy states usage detected

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
  • Add a meaningful evidence note: what changed, where it was tested, and proof/reference.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

Summary: This XML file uses states. In newer Odoo versions, this may need conversion depending on context. Phase 61 recommendation: Review states-based visibility/read-only logic and convert where required for the target Odoo version. Action category: review_convert_states_modifiers. Confidence: medium. Review status: manual-review.

Developer task: Review scanner finding for erpweb_phase3_risky_test_module. Location: erpweb_phase3_risky_test_module/views/risky_views.xml:5. Suggested action: Review state-based visibility/read-only logic for compatibility with the target Odoo version. Use Phase 61 action category 'review_convert_states_modifiers' to group and sequence this work. Manual-review status: manual-review.

Acceptance criteria / evidence required:

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.

Source: Phase 61 scanner recommendation / review_convert_states_modifiers

Trace key: scanner:erpweb_phase3_risky_test_module|xml_views|Legacy states usage detected|erpweb_phase3_risky_test_module/views/risky_views.xml|5

Open module · Open scan source

Seq 52 Low Scanner Finding To Do 1.00h erpweb_phase3_risky_test_module Update Manifest Version for Target Manual Review Not Ready

#9 — Manifest version does not start with source Odoo major version

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
  • Add a meaningful evidence note: what changed, where it was tested, and proof/reference.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

Summary: Project source version is 16.0, but manifest version is 12.0.1.0.0. Phase 61 recommendation: Review and update the manifest version so it aligns with the source and target upgrade path. Action category: update_manifest_version_for_target. Confidence: medium. Review status: manual-review.

Developer task: Review scanner finding for erpweb_phase3_risky_test_module. Location: erpweb_phase3_risky_test_module/__manifest__.py. Suggested action: Confirm whether the manifest version is correct for the source branch being upgraded. Use Phase 61 action category 'update_manifest_version_for_target' to group and sequence this work. Manual-review status: manual-review.

Acceptance criteria / evidence required:

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.

Source: Phase 61 scanner recommendation / update_manifest_version_for_target

Trace key: scanner:erpweb_phase3_risky_test_module|version_risk|Manifest version does not start with source Odoo major version|erpweb_phase3_risky_test_module/__manifest__.py|

Open module · Open scan source

Seq 62 Info Scanner Finding To Do 0.00h erpweb_phase3_risky_test_module Dependency Review Manual Review Not Ready

#2 — Dependencies captured

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
  • Add a meaningful evidence note: what changed, where it was tested, and proof/reference.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

Summary: Dependencies recorded: stock, sale, account, mail Phase 61 recommendation: Use the source-aware dependency graph to validate dependency availability before code migration. Action category: dependency_review. Confidence: high. Review status: auto-safe.

Developer task: Review scanner finding for erpweb_phase3_risky_test_module. Location: custom_addons/qr_delivery/__manifest__.py. Suggested action: In the dependency graph phase, split and validate these dependencies against target Odoo version availability. Use Phase 61 action category 'dependency_review' to group and sequence this work. Manual-review status: auto-safe.

Acceptance criteria / evidence required:

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.

Source: Phase 61 scanner recommendation / dependency_review

Trace key: scanner:erpweb_phase3_risky_test_module|dependencies|Dependencies captured|custom_addons/qr_delivery/__manifest__.py|

Open module · Open scan source

Seq 62 Info Scanner Finding To Do 0.00h erpweb_phase3_risky_test_module Dependency Review Manual Review Not Ready

#3 — Structured dependency records rebuilt

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
  • Add a meaningful evidence note: what changed, where it was tested, and proof/reference.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

Summary: Structured dependency records were rebuilt for this module. Created: 0. Updated: 2. Deleted stale: 0. Standard Odoo: 2. Uploaded providers: 0. Missing custom: 0. Phase 61 recommendation: Use the source-aware dependency graph to validate dependency availability before code migration. Action category: dependency_review. Confidence: high. Review status: auto-safe.

Developer task: Review scanner finding for erpweb_phase3_risky_test_module. Location: erpweb_phase3_risky_test_module/__manifest__.py. Suggested action: Review the dependency summary report for missing custom dependencies before starting code migration. Use Phase 61 action category 'dependency_review' to group and sequence this work. Manual-review status: auto-safe.

Acceptance criteria / evidence required:

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.

Source: Phase 61 scanner recommendation / dependency_review

Trace key: scanner:erpweb_phase3_risky_test_module|dependencies|Structured dependency records rebuilt|erpweb_phase3_risky_test_module/__manifest__.py|

Open module · Open scan source

Seq 62 Info Scanner Finding To Do 0.00h erpweb_phase3_risky_test_module Dependency Review Manual Review Not Ready

#4 — Dependencies detected

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
  • Add a meaningful evidence note: what changed, where it was tested, and proof/reference.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

Summary: Dependencies found in manifest: base, sale Phase 61 recommendation: Use the source-aware dependency graph to validate dependency availability before code migration. Action category: dependency_review. Confidence: high. Review status: auto-safe.

Developer task: Review scanner finding for erpweb_phase3_risky_test_module. Location: erpweb_phase3_risky_test_module/__manifest__.py. Suggested action: Later phases should validate these dependencies against the target Odoo version and installed app set. Use Phase 61 action category 'dependency_review' to group and sequence this work. Manual-review status: auto-safe.

Acceptance criteria / evidence required:

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.

Source: Phase 61 scanner recommendation / dependency_review

Trace key: scanner:erpweb_phase3_risky_test_module|dependencies|Dependencies detected|erpweb_phase3_risky_test_module/__manifest__.py|

Open module · Open scan source

Seq 62 Info Scanner Finding To Do 0.00h erpweb_phase3_risky_test_module Dependency Review Manual Review Not Ready

#5 — Dependencies detected

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
  • Add a meaningful evidence note: what changed, where it was tested, and proof/reference.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

Summary: Dependencies found in manifest: base, sale, stock Phase 61 recommendation: Use the source-aware dependency graph to validate dependency availability before code migration. Action category: dependency_review. Confidence: high. Review status: auto-safe.

Developer task: Review scanner finding for erpweb_phase3_risky_test_module. Location: erpweb_phase3_test_module/__manifest__.py. Suggested action: Later phases should validate these dependencies against target Odoo version and installed app set. Use Phase 61 action category 'dependency_review' to group and sequence this work. Manual-review status: auto-safe.

Acceptance criteria / evidence required:

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.

Source: Phase 61 scanner recommendation / dependency_review

Trace key: scanner:erpweb_phase3_risky_test_module|dependencies|Dependencies detected|erpweb_phase3_test_module/__manifest__.py|

Open module · Open scan source

Seq 62 Info Scanner Finding To Do 0.00h erpweb_phase3_risky_test_module Validate Manifest Metadata Manual Review Not Ready

#6 — Manifest metadata captured

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
  • Add a meaningful evidence note: what changed, where it was tested, and proof/reference.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

Summary: Module 'QR Delivery Updated' has manifest metadata captured. Manifest version: 16.0.1.0.1. Phase 61 recommendation: Validate manifest metadata, dependencies, assets, license, and version format for the target Odoo version. Action category: validate_manifest_metadata. Confidence: medium. Review status: manual-review.

Developer task: Review scanner finding for erpweb_phase3_risky_test_module. Location: custom_addons/qr_delivery/__manifest__.py. Suggested action: In the real scanner phase, parse this manifest and validate depends, assets, license and version format. Use Phase 61 action category 'validate_manifest_metadata' to group and sequence this work. Manual-review status: manual-review.

Acceptance criteria / evidence required:

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.

Source: Phase 61 scanner recommendation / validate_manifest_metadata

Trace key: scanner:erpweb_phase3_risky_test_module|manifest|Manifest metadata captured|custom_addons/qr_delivery/__manifest__.py|

Open module · Open scan source

Seq 62 Info Scanner Finding To Do 0.00h erpweb_phase3_risky_test_module Validate Manifest Metadata Manual Review Not Ready

#7 — Manifest parsed successfully

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
  • Add a meaningful evidence note: what changed, where it was tested, and proof/reference.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

Summary: Module metadata was parsed safely. Version: 12.0.1.0.0. License: LGPL-3. Phase 61 recommendation: Validate manifest metadata, dependencies, assets, license, and version format for the target Odoo version. Action category: validate_manifest_metadata. Confidence: medium. Review status: manual-review.

Developer task: Review scanner finding for erpweb_phase3_risky_test_module. Location: erpweb_phase3_risky_test_module/__manifest__.py. Suggested action: Continue with dependency and code-pattern scanning. Use Phase 61 action category 'validate_manifest_metadata' to group and sequence this work. Manual-review status: manual-review.

Acceptance criteria / evidence required:

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.

Source: Phase 61 scanner recommendation / validate_manifest_metadata

Trace key: scanner:erpweb_phase3_risky_test_module|manifest|Manifest parsed successfully|erpweb_phase3_risky_test_module/__manifest__.py|

Open module · Open scan source

Seq 62 Info Scanner Finding To Do 0.00h erpweb_phase3_risky_test_module Validate Manifest Metadata Manual Review Not Ready

#8 — Manifest parsed successfully

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • Manual-review package is not yet in Review or Done.
  • No tracking evidence note is available yet.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Record the developer decision, target-version test result, and proof/reference.
  • Add a meaningful evidence note: what changed, where it was tested, and proof/reference.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

Summary: Version: 16.0.1.0.0. License: LGPL-3. Phase 61 recommendation: Validate manifest metadata, dependencies, assets, license, and version format for the target Odoo version. Action category: validate_manifest_metadata. Confidence: medium. Review status: manual-review.

Developer task: Review scanner finding for erpweb_phase3_risky_test_module. Location: erpweb_phase3_test_module/__manifest__.py. Suggested action: Continue with dependency and code-pattern scanning. Use Phase 61 action category 'validate_manifest_metadata' to group and sequence this work. Manual-review status: manual-review.

Acceptance criteria / evidence required:

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.

Source: Phase 61 scanner recommendation / validate_manifest_metadata

Trace key: scanner:erpweb_phase3_risky_test_module|manifest|Manifest parsed successfully|erpweb_phase3_test_module/__manifest__.py|

Open module · Open scan source

Seq 65 Info Dependency To Do 0.50h erpweb_phase3_risky_test_module Keep Dependency Auto-safe Not Ready

#16 — Dependency upgrade recommendation: base

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • No tracking evidence note is available yet.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Add a meaningful evidence note: what changed, where it was tested, and proof/reference.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

Summary: erpweb_phase3_risky_test_module depends on base. Action category: keep_dependency. Status: auto-safe. Confidence: high. Classification: available_in_target_community.

Developer task: Keep this dependency. It exists in both the validated source and target Odoo source registries. Source availability: True; target availability: True; community: True; enterprise: False. Source edition: community; target edition: community. Manual review required: auto-safe.

Acceptance criteria / evidence required:

Dependency recommendation has been reviewed against the validated source and target Odoo source registries. Required dependency action is documented in the module manifest or upgrade notes. If Enterprise or custom dependency handling is required, the target test environment includes the required addons. Dependency graph and upgrade recommendation dashboard are rebuilt after changes.

Source: Phase 61 dependency recommendation / keep_dependency

Trace key: upgrade-rec:dependency:erpweb_phase3_risky_test_module:base:keep_dependency

Seq 65 Info Dependency To Do 0.50h erpweb_phase3_risky_test_module Keep Dependency Auto-safe Not Ready

#17 — Dependency upgrade recommendation: sale

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • No developer is assigned.
  • No tracking evidence note is available yet.

Missing action/evidence:

  • Assign the package and move it through In Progress or Review before Done.
  • Move the package to Review once the developer believes it is closure-ready.
  • Assign an accountable developer before closure.
  • Add a meaningful evidence note: what changed, where it was tested, and proof/reference.
Completion gate: selecting Done requires evidence. Add what changed, where it was tested, and the proof/reference before saving. Quality gate: evidence must be meaningful, not only ok/done/fixed. Include proof such as commit, build, screenshot, log, report, scanner output, or URL/reference.

Summary: erpweb_phase3_risky_test_module depends on sale. Action category: keep_dependency. Status: auto-safe. Confidence: high. Classification: available_in_target_community.

Developer task: Keep this dependency. It exists in both the validated source and target Odoo source registries. Source availability: True; target availability: True; community: True; enterprise: False. Source edition: community; target edition: community. Manual review required: auto-safe.

Acceptance criteria / evidence required:

Dependency recommendation has been reviewed against the validated source and target Odoo source registries. Required dependency action is documented in the module manifest or upgrade notes. If Enterprise or custom dependency handling is required, the target test environment includes the required addons. Dependency graph and upgrade recommendation dashboard are rebuilt after changes.

Source: Phase 61 dependency recommendation / keep_dependency

Trace key: upgrade-rec:dependency:erpweb_phase3_risky_test_module:sale:keep_dependency

Execution by Action Category

Use this section to batch similar upgrade fixes, such as old API conversion, XML modifier review, JavaScript migration, or dependency confirmation.

Score 299

Category: score 299 Total: 1 Open: 1 Manual-review: 1 Auto-safe: 0 6.00h
Seq Priority Module Package Review Status
20 Critical erpweb_phase3_risky_test_module #15 — Developer upgrade review: erpweb_phase3_risky_test_module Manual Review To Do

Convert Old API Signatures

Category: convert_old_api_signature Total: 1 Open: 1 Manual-review: 1 Auto-safe: 0 2.00h
Seq Priority Module Package Review Status
32 High erpweb_phase3_risky_test_module #1 — Old Odoo API method signature detected Manual Review To Do

Migrate Legacy JavaScript Module Pattern

Category: migrate_legacy_javascript_module Total: 1 Open: 1 Manual-review: 1 Auto-safe: 0 2.00h
Seq Priority Module Package Review Status
42 Medium erpweb_phase3_risky_test_module #10 — Legacy Odoo JavaScript module pattern detected Manual Review To Do

Migrate Legacy web.* JavaScript Imports

Category: migrate_legacy_web_js_imports Total: 1 Open: 1 Manual-review: 1 Auto-safe: 0 2.00h
Seq Priority Module Package Review Status
42 Medium erpweb_phase3_risky_test_module #11 — Legacy web.* JavaScript require detected Manual Review To Do

Modernize Recordset API

Category: modernize_recordset_api Total: 1 Open: 1 Manual-review: 1 Auto-safe: 0 2.00h
Seq Priority Module Package Review Status
42 Medium erpweb_phase3_risky_test_module #12 — Deprecated @api.multi usage Manual Review To Do

Review / Convert attrs Modifiers

Category: review_convert_attrs_modifiers Total: 1 Open: 1 Manual-review: 1 Auto-safe: 0 2.00h
Seq Priority Module Package Review Status
42 Medium erpweb_phase3_risky_test_module #14 — Legacy attrs usage detected Manual Review To Do

Review / Convert states Modifiers

Category: review_convert_states_modifiers Total: 1 Open: 1 Manual-review: 1 Auto-safe: 0 2.00h
Seq Priority Module Package Review Status
42 Medium erpweb_phase3_risky_test_module #13 — Legacy states usage detected Manual Review To Do

Update Manifest Version for Target

Category: update_manifest_version_for_target Total: 1 Open: 1 Manual-review: 1 Auto-safe: 0 1.00h
Seq Priority Module Package Review Status
52 Low erpweb_phase3_risky_test_module #9 — Manifest version does not start with source Odoo major version Manual Review To Do

Dependency Review

Category: dependency_review Total: 4 Open: 4 Manual-review: 4 Auto-safe: 0 0.00h
Seq Priority Module Package Review Status
62 Info erpweb_phase3_risky_test_module #2 — Dependencies captured Manual Review To Do
62 Info erpweb_phase3_risky_test_module #3 — Structured dependency records rebuilt Manual Review To Do
62 Info erpweb_phase3_risky_test_module #4 — Dependencies detected Manual Review To Do
62 Info erpweb_phase3_risky_test_module #5 — Dependencies detected Manual Review To Do

Validate Manifest Metadata

Category: validate_manifest_metadata Total: 3 Open: 3 Manual-review: 3 Auto-safe: 0 0.00h
Seq Priority Module Package Review Status
62 Info erpweb_phase3_risky_test_module #6 — Manifest metadata captured Manual Review To Do
62 Info erpweb_phase3_risky_test_module #7 — Manifest parsed successfully Manual Review To Do
62 Info erpweb_phase3_risky_test_module #8 — Manifest parsed successfully Manual Review To Do

Keep Dependency

Category: keep_dependency Total: 2 Open: 2 Manual-review: 0 Auto-safe: 2 1.00h
Seq Priority Module Package Review Status
65 Info erpweb_phase3_risky_test_module #16 — Dependency upgrade recommendation: base Auto-safe To Do
65 Info erpweb_phase3_risky_test_module #17 — Dependency upgrade recommendation: sale Auto-safe To Do

Evidence & Acceptance Rules Before Marking Complete

Manual-review items: require developer notes explaining the code decision, before/after module evidence, rebuilt scanner/dependency/risk output, and target-version test confirmation where applicable.

Auto-safe items: can be confirmed later, but must still show the dependency or manifest decision was reviewed against the validated source/target repositories.

Done means: the work package acceptance criteria is satisfied, evidence exists in the project notes/history, and related reports have been rebuilt.

This page is advisory and tracking-focused. It does not modify uploaded module code automatically.