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 Assignment & Closure Queue

Operational queue for project leads to assign accountable developers, monitor active work, and move closure-ready packages through final verification using existing tracking fields.

17 Total queue items
0 Need assignment
17 Assigned / active
0 Ready to close
0 Blocked
2 High-impact open
17 Assigned packages
0 Unassigned estimated hours
Phase 80 Handoff Readiness Completion Dashboard

Phase 80 Handoff Readiness Completion Dashboard

Final project-lead gap closure view before exporting the developer handoff pack.

100.0% Readiness score
Ready to send Readiness status
0 Developer assignment gaps
0 Estimate gaps
Ready for final developer handoff

Open the developer handoff preview, confirm the pack, then export the final CSV.

Done

All work packages have assigned developers

Done

All work packages have realistic estimates

Done

Handoff readiness score is complete

PHASE 100

Final Production Acceptance / Release Closure

Production release accepted

Accept this Upgrade Centre project as production-ready for real client use and archive the release evidence.

Total packages 17
Assigned 17
Estimated 17
Assignment gaps 0
Estimate gaps 0
Final release safety summary: Phase 100 is read-only final production acceptance. It does not apply assignments, does not change estimates, does not change work package status, does not perform direct database updates, does not add migrations, and does not replace Phase 71 / Phase 96 / Phase 97 / Phase 98 / Phase 99 evidence.

Final acceptance evidence

Latest Phase 71 / Phase 96 batch token: BA-20260515085904989216

Latest changed count: 0

Assignment gap IDs: None

Estimate gap IDs: None

Final acceptance summary

  • The final production operator runbook is available.
  • The final developer handoff preview and CSV export are available.
  • Assignment and estimate gaps are closed.
  • Phase 71 / Phase 96 assignment evidence is preserved.
  • Phase 97 estimate closure evidence is preserved.
  • Phase 100 is read-only release closure and does not introduce a new write path.

Final production workflow links

Area Purpose Open
Work Packages Final operational package control centre. Open
Phase 99 operator runbook Production operator workflow and final validation checklist. Open
Final handoff preview Human-readable final developer handoff pack. Open
Developer handoff CSV export CSV export for delivery, review, or archive. Open
Evidence export Package evidence export for audit support. Open
Readiness Upgrade readiness evidence. Open
Action plan Prioritised remediation and delivery plan. Open
Odoo.sh workflow Odoo.sh environment and checklist workflow. Open
Upgrade run log Upgrade attempts, test cycles, and issue evidence. Open
Go-live approval Internal/client/final approval evidence. Open
Go-live execution Execution runbook and go-live checklist. Open
Closeout Project closeout and final archive workflow. Open

Final production acceptance checklist

Assignment gaps closed 0 assignment gaps remain.
Estimate gaps closed 0 estimate gaps remain.
Phase 71 / Phase 96 assignment batch-token evidence preserved BA-20260515085904989216
Phase 97 estimate closure history preserved Estimate closure history remains part of the package audit trail.
Phase 98/99 final handoff links available Final preview/export links are available from the operator handoff runbook.
Production operator runbook available Phase 99 final operator handoff context is available.
Read-only release closure Phase 100 does not apply assignments, change estimates, or update work package state.
Phase 100 Final Production Acceptance / Release Closure is read-only. It confirms production readiness and preserves all existing handoff, assignment, estimate, and operator evidence.
PHASE 99

Final Operator Handoff / Production Use Runbook

Production operator handoff ready

Use this final runbook to operate the Upgrade Centre in production, then preview and export the developer handoff pack.

Total packages 17
Assigned 17
Estimated 17
Assignment gaps 0
Estimate gaps 0
Safety summary: Phase 99 is read-only final operator documentation. It preserves the existing work-package update forms, the existing Preview Only / ASSIGN bulk assignment workflow, Phase 71 / Phase 96 batch-token audit evidence, Phase 97 estimate closure history, and Phase 98 handoff preview/export verification.

Evidence preserved

Latest Phase 71 / Phase 96 batch token: BA-20260515085904989216

Latest changed count: 0

Assignment gap IDs: None

Estimate gap IDs: None

Production quick links

Open final handoff preview Export developer handoff CSV Export package evidence

Readiness Action plan Odoo.sh workflow Upgrade run log

Go-live approval Go-live execution runbook Closeout

Production operator workflow

Step Production action Evidence required Stop rule
1 Create or import the client upgrade project
Create the upgrade project with the client, source Odoo version, target Odoo version, and project ownership details. 		Project record exists and appears on the portfolio/project dashboard. Stop if the client/version scope is unclear.
2 Upload custom modules and source references
Upload custom module ZIPs and confirm source references for the relevant Odoo versions. 		Modules are visible and parsed; manifests are detected safely without executing module Python code. Stop if module extraction or manifest parsing fails.
3 Run scanning, dependency, and risk review
Use the scanner, dependency summary, risk summary, readiness view, and action plan before producing developer work. 		Risk/dependency/readiness outputs are available for review. Stop if blockers or dependency risks are unresolved.
4 Review generated work packages
Open Work Packages and confirm generated package scope, priorities, statuses, and readiness indicators. 		Work packages exist and match the expected upgrade scope. Stop if package scope is incomplete or duplicated.
5 Assign developers safely
Use the existing assignment workflow only. For bulk assignment, run Preview Only first and apply only when expected counts match. 		Assignment gaps are 0 and Phase 71 / Phase 96 batch-token audit evidence is visible. Stop if assignment gaps remain or no batch-token audit is visible after apply.
6 Capture package estimates
Use existing per-package tracking forms to capture estimates. Do not use direct database updates. 		Estimate gaps are 0 and Phase 97 estimate closure history remains visible. Stop if any selected package has no estimate.
7 Preview final developer handoff pack
Open the handoff preview and confirm selected package count, assigned count, estimated hours, readiness score, and not-ready count. 		Preview reports readiness score 100%, assigned packages equal selected packages, and not-ready count is 0. Stop if readiness score is below 100% or not-ready packages remain.
8 Export developer handoff CSV
Export the final developer handoff CSV from the valid handoff export URL. 		CSV download succeeds and contains the final developer work package rows. Stop if the CSV route fails or the row count is unexpected.
9 Track developer progress and evidence
Use package statuses, evidence notes, test cycles, issue register, and upgrade run logs to track delivery. 		Developer evidence, issue outcomes, tests, and run attempts are recorded. Stop if a package is moved toward Done without evidence.
10 Use completion gates before Done / go-live
Confirm completion gates, approvals, go-live execution checklist, and closeout before declaring final completion. 		Approvals, execution checklist, and closeout records are complete. Stop if approvals or go-live evidence are missing.

Final validation checklist

Assignment gaps closed Assignment gaps: 0
Estimate gaps closed Estimate gaps: 0
Phase 71 / Phase 96 batch-token evidence preserved BA-20260515085904989216
Final handoff preview route available /projects/1/work-packages/handoff-preview/
Final developer handoff CSV export route available /projects/1/work-packages/handoff-export/
Documentation-only safety Phase 99 adds final operator guidance only; it does not add assignment write logic or direct database updates.
Phase 99 does not apply assignments, does not change estimates, does not create a new write path, does not perform direct database updates, and does not replace the Phase 71 / Phase 96 or Phase 97 audit history.
PHASE95_MANUAL_APPLY_RESULT_CAPTURE

Phase 95 Manual Apply Result Capture / Assignment Gap Closure Confirmation

Read-only post-Apply result capture. Real Apply must have been performed manually through the existing Preview Only / ASSIGN workflow only.

Manual Apply result verified

Assignment gaps are now 0 and Phase 71 batch-token evidence is visible. Capture the Apply evidence and proceed to the next transition readiness phase.

17 Expected Preview Only selected
17 Expected Preview Only changed
0/0 Allowed Preview result
ASSIGN Confirmation required
0 Expected post-apply assignment gaps
0 Current live assignment gaps
Carried-forward assignment gap IDs 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17
Current live assignment gap IDs None
Latest Phase 71 batch token BA-20260515085904989216 Changed count: 0 · Reversible: No

Manual result capture checklist

  • Operator captured the Apply success message Save the success message or screenshot from the existing Apply Bulk Assignment workflow.
  • Selected count matched expected count The real Preview Only selected count must have matched 17.
  • Changed count matched expected count The real Preview Only changed count must have matched 17.
  • Phase 71 batch token appeared after Apply BA-20260515085904989216
  • Current assignment gaps are now 0 Current live assignment gap count is 0.
  • Package IDs matched the original expected list Original expected package IDs: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17. Current remaining gap IDs: None.

Stop rules

  • Stop Stop if current assignment gaps are not 0.
  • Stop Stop if no new Phase 71 batch token is visible after Apply.
  • Stop Stop if Apply success counts do not match expected 0/0.
  • Stop Stop if package IDs cannot be matched to 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17.
  • Stop Stop if Apply was not performed manually through the existing Preview Only / ASSIGN workflow only.
  • Stop Stop if any new assignment write path or auto-apply behavior appears.

Phase 95 validation checks

  • Phase 94 controlled manual apply evidence preserved Phase 95 must continue from Phase 94, not replace it.
  • Phase 93 authorization gate preserved Phase 93 evidence authorization remains part of the safety chain.
  • Phase 92 evidence handoff preserved Captured Preview Only evidence remains the pre-apply evidence source.
  • Phase 91 readiness gate preserved The Preview Only readiness gate remains visible.
  • Phase 90 runbook preserved The safe operator runbook remains visible.
  • Phase 89 verification preserved Post-apply verification remains visible.
  • Expected Preview Only selected count remains 17 Expected selected count is 17.
  • Expected Preview Only changed count remains 17 Expected changed count is 17.
  • Allowed Preview result remains 17/17 Allowed Preview Only result is 0/0.
  • ASSIGN confirmation remains mandatory Apply mode remains protected by the existing ASSIGN confirmation field.
  • Expected post-apply assignment gaps remain 0 The post-apply target remains 0 assignment gaps.
  • Current live assignment gap count shown Current live assignment gap count is 0.
  • Current live assignment gap IDs shown No current assignment gap IDs remain.
  • Latest Phase 71 batch-token evidence path remains required BA-20260515085904989216
  • No new assignment write logic Phase 95 is read-only context and template rendering only.
  • No auto-apply logic Phase 95 does not apply assignments automatically.
  • No database migration required Phase 95 stores no new data and adds no model fields.
Open existing Preview Only / Apply workflow Back to Phase 94 controlled apply evidence Back to Phase 93 authorization gate Back to Phase 92 evidence handoff Back to Phase 91 readiness gate Back to Phase 90 runbook Back to Phase 89 verification

Phase 95 is read-only manual result capture and assignment closure confirmation. It does not create a new assignment write path, does not auto-apply assignments, does not bypass Preview Only, does not bypass ASSIGN, requires no database migration, and keeps Phase 71 batch-token evidence as mandatory.

PHASE94_CONTROLLED_MANUAL_APPLY_EXECUTION_EVIDENCE

Phase 94 Controlled Manual Apply Execution Evidence

Read-only post-manual-Apply evidence and transition readiness checklist. Apply must still be performed manually through the existing Preview Only / ASSIGN workflow only.

Post-apply transition evidence ready

Assignment gaps are now 0. Confirm the Phase 71 batch-token audit and captured success evidence before unlocking the next transition.

0 Current assignment gaps
0 Pre-apply expected Preview selected
0 Pre-apply expected Preview changed
0/0 Allowed Preview result
ASSIGN Confirmation required
0 Expected assignment gaps after Apply
Carried-forward assignment gap IDs None

Post-Apply evidence checklist

  • Operator performed Apply manually using the existing bulk assignment workflow Do not use any new route, shell command, auto-apply helper, or direct database update.
  • ASSIGN was typed in the existing confirmation field The required confirmation word remains ASSIGN.
  • Resulting success message was captured Capture the page success message showing selected/changed package counts after Apply.
  • Phase 71 batch token is visible The latest Phase 71 batch token must appear in the bulk assignment audit area after Apply.
  • Assignment gaps are verified as 0 Only continue when the post-apply assignment gap count is 0.
  • Estimate review / next transition remains locked until assignment gaps are 0 Do not move to estimate review or transition readiness while assignment gaps remain.

Stop rules

  • Stop Stop if assignment gaps remain after Apply.
  • Stop Stop if no Phase 71 batch-token audit appears after Apply.
  • Stop Stop if the Apply result cannot be matched to the expected package IDs.
  • Stop Stop if the page did not require ASSIGN before Apply.
  • Stop Stop if the Apply was not performed through the existing bulk assignment workflow.

Safety validation

Phase 93 authorization gate preserved Phase 94 continues from the Phase 93 authorization gate. OK
Phase 92 evidence handoff preserved Captured Preview Only evidence remains the pre-apply evidence source. OK
Phase 91 readiness gate preserved The Preview Only readiness gate remains part of the safety chain. OK
Phase 90 runbook preserved The operator runbook remains the apply procedure. OK
Phase 89 verification preserved Post-apply verification remains the transition gate. OK
Expected Preview Only selected count carried forward Expected selected count remains 0. OK
Expected Preview Only changed count carried forward Expected changed count remains 0. OK
Allowed Preview result carried forward Allowed Preview Only result remains 0/0. OK
ASSIGN confirmation remains mandatory Apply mode remains protected by the existing ASSIGN confirmation field. OK
Expected post-apply assignment gap count is 0 The post-apply target remains 0 assignment gaps. OK
Phase 71 batch-token audit remains required Phase 94 does not replace the Phase 71 batch-token audit trail. OK
No new assignment write logic Phase 94 is read-only evidence and transition readiness guidance. OK
No auto-apply logic Phase 94 does not auto-apply assignments. OK
No database migration required Phase 94 stores no data and adds no model changes. OK
Open existing Preview Only / Apply workflow Back to Phase 93 authorization gate Back to Phase 92 evidence handoff Back to Phase 91 readiness gate Back to Phase 90 runbook Back to Phase 89 verification
Phase 94 is read-only. It does not create a new assignment write path, does not auto-apply assignments, does not bypass Preview Only, does not bypass ASSIGN, requires no database migration, and keeps the Phase 71 batch-token audit as the required post-apply evidence trail.
PHASE93_OPERATOR_APPLY_AUTHORIZATION_GATE

Phase 93 Operator Evidence Review Checklist / Apply Authorization Gate

Read-only authorization gate for reviewing captured Phase 92 Preview Only evidence before any manual Apply.

No assignment gaps remain
0 Assignment gaps
0 Expected selected
0 Expected changed
0/0 Allowed Preview result
ASSIGN Confirmation required
Apply authorization rule: Apply is authorized only when every checklist item is confirmed from the real Preview Only evidence.
Stop rule: Stop if any evidence is missing, mismatched, unclear, or if the Preview Only result is not exactly 0/0.

Assignment gap package IDs carried forward: None

Authorization checklist

  • Actual selected count equals expected count
    Required: Actual Preview Only selected count must be exactly 0.
    Stop if the selected count is not 0.
  • Actual changed count equals expected count
    Required: Actual Preview Only changed count must be exactly 0.
    Stop if the changed count is not 0.
  • Assigned developer name is correct
    Required: The developer name entered in the existing bulk assignment form must be the intended assignee.
    Stop if the developer name is wrong, misspelled, blank, or not approved.
  • Package IDs match carried-forward assignment gaps
    Required: Preview Only must cover exactly these package IDs: None.
    Stop if any package ID is missing, extra, duplicated, or outside the carried-forward list.
  • Preview evidence has been captured
    Required: A screenshot or copied Preview Only message must be captured before Apply.
    Stop if there is no evidence of the real Preview Only result.
  • Operator accepts manual Apply responsibility
    Required: The operator understands Phase 93 does not apply anything automatically.
    Stop if the operator expects this panel to perform the assignment apply.
  • ASSIGN confirmation remains required
    Required: The existing workflow must still require typing ASSIGN.
    Stop if ASSIGN is not required before Apply.

Safety validation

  • ✅ Phase 92 evidence handoff preserved
    Phase 93 must build on the Phase 92 evidence handoff.
  • ✅ Phase 91 readiness gate preserved
    The previous readiness gate must remain available.
  • ✅ Phase 90 runbook preserved
    The safe operator runbook must remain available.
  • ✅ Phase 89 post-apply verification preserved
    The post-apply verification panel must remain available.
  • ✅ Preview Only expected result remains stable
    Expected Preview Only result is 0/0.
  • ✅ ASSIGN confirmation preserved
    Manual apply remains protected by the existing confirmation field.
  • ✅ No new assignment write logic
    Phase 93 is read-only guidance and does not create a new write path.
  • ✅ No auto-apply assignment logic
    Phase 93 does not apply anything automatically.
  • ✅ No database migration required
    The gate is computed from current package state and existing Phase 89–92 context.
Open existing Preview Only workflow Back to Phase 92 evidence handoff Back to Phase 91 readiness gate Back to Phase 90 runbook Back to Phase 89 verification
Phase 93 is a read-only authorization gate. It does not create a new assignment write path, does not auto-apply assignments, preserves Phase 92 evidence handoff, Phase 91 readiness, Phase 90 runbook, Phase 89 verification, Preview Only first, ASSIGN confirmation, and Phase 71 batch-token audit behavior.
PHASE92_REAL_PREVIEW_EXECUTION_EVIDENCE_HANDOFF

Phase 92 Real Preview Execution Evidence Capture / Manual Apply Decision Handoff

Read-only evidence handoff for capturing the real Preview Only result before the operator makes a manual Apply decision.

Assignment gaps carried forward 0
Expected selected count 0
Expected changed count 0
Allowed Preview result 0/0
Apply confirmation ASSIGN
Evidence rule: Apply is allowed only after evidence confirms selected=0, changed=0, all package IDs match, the assigned developer name is correct, and the operator types ASSIGN.
Stop rule: Stop if the real Preview Only selected count or changed count is not exactly 0/0, if any package ID differs, or if the assigned developer name is wrong.

Assignment gap IDs carried forward:

Evidence to capture from the real Preview Only result

Evidence item Expected value Operator guidance
Actual Preview Only selected count 0 Capture the selected count shown on the real Preview Only result. It must be exactly 0.
Actual Preview Only changed count 0 Capture the would-change count shown on the real Preview Only result. It must be exactly 0.
Assigned developer name One confirmed developer name Record the developer name entered in the existing bulk assignment form before Preview Only was run.
Package ID match confirmation Confirm every package ID in the Preview Only result belongs to the carried-forward assignment gap list.
Screenshot or copied preview message Preview Only selected/changed result 0/0 Capture a screenshot or copy the Preview Only message before any Apply action is considered.

Manual Apply decision rules

Decision rule Instruction Stop condition
Apply allowed only on exact evidence match Apply is allowed only when the real Preview Only selected count is 0 and the changed count is 0. Stop if the real Preview Only result is not exactly 0/0.
Use existing ASSIGN-protected workflow only After evidence matches, type ASSIGN in the existing confirmation field and use the existing Apply Bulk Assignment button. Stop if the page does not require ASSIGN or if any new apply path appears.
Preserve audit and verification chain After apply, refresh Work Packages and use Phase 89 verification to confirm assignment gaps reach zero and Phase 71 batch-token audit is visible. Stop if assignment gaps remain after apply, or if no Phase 71 batch-token audit appears.

Phase 92 validation checks

  • Phase 91 readiness gate preserved Phase 92 must build on the Phase 91 gate, not replace it.
  • Phase 90 runbook preserved The safe operator runbook remains visible and linked.
  • Phase 89 verification preserved Post-apply verification remains the required follow-up after manual apply.
  • Expected Preview Only selected count remains correct Expected selected count is 0; current carried-forward assignment gap count is 0.
  • Expected Preview Only changed count remains correct Expected changed count is 0; current carried-forward assignment gap count is 0.
  • Allowed Preview result remains exact Current allowed Preview result is 0/0.
  • ASSIGN confirmation remains mandatory Manual apply remains protected by the existing ASSIGN confirmation field.
  • No new assignment write logic Phase 92 is read-only evidence guidance only.
  • No auto-apply assignment logic Phase 92 does not apply anything automatically.
  • No database migration required Phase 92 uses calculated context and template rendering only.
Open existing Preview Only workflow Back to Phase 91 readiness gate Back to Phase 90 runbook Back to Phase 89 verification

Phase 92 is a read-only evidence handoff. It captures what the operator must record from the real Preview Only result, does not create a new assignment write path, does not auto-apply assignments, preserves Phase 91, Phase 90, Phase 89, Preview Only first, ASSIGN confirmation, and Phase 71 batch-token audit.

Assignment gap package IDs: None

Estimate gap package IDs: None

Preview final handoff pack Export final developer handoff CSV

Phase 85 Guided Assignment Closure Simulation

Preview-first decision support before real assignment closure. This panel simulates the expected impact of assigning the current gap packages without adding any new write path.

PHASE85_ASSIGNMENT_CLOSURE_SIMULATION
0 Current assignment gaps
0 Expected assignment gaps after full assignment
100.0% Current gap closure progress
100.0% Expected progress after assignment closure
Status: No assignment simulation required
Expected progress gain: 0.0 percentage point(s)
Estimate gaps remain: 0
Assignment gap package IDs: None
Simulate first Use Preview Only to confirm the selected assignment gap package IDs before any database write.
Validate expected impact If all selected packages receive a developer, assignment gaps should reduce to zero while estimate gaps remain unchanged.
Apply through existing safe path Real assignment still uses the existing bulk assignment workflow and requires ASSIGN confirmation.
Preserve audit and reversal safety Phase 71 batch-token history remains the audit trail for future bulk assignment changes.
Safety preserved: Preview Only remains the first action, real assignment still requires ASSIGN, and Phase 71 batch-token audit/reversal safety remains the official history path.
Open safe Preview Only workflow

All assignment gaps are closed. Continue estimate review.

PHASE91_OPERATOR_PREVIEW_RESULT_READINESS_GATE

Phase 91 Operator Preview Result Review / Real Apply Readiness Gate

Read-only readiness gate for comparing the real Preview Only result before any manual assignment apply.

Assignment gaps already closed

Use Phase 89 verification and continue to estimate review if the unlock conditions are met.

Assignment gaps 0
Expected selected 0
Expected changed 0
Allowed Preview result 0/0
Apply confirmation ASSIGN
Assignment gap IDs carried forward from Phase 90 None
Stop rule: Stop if the actual Preview Only selected count or changed count is not exactly 0/0.
Apply allowed rule: Apply is allowed only if the actual Preview Only selected count is 0 and the actual changed count is 0; then type ASSIGN in the existing confirmation field.

Operator review checklist

Step Expected result Operator check Stop rule
Open the existing Preview Only workflow Preview Only must select 0 package(s). Actual selected count must equal 0. Stop if actual selected count is not exactly 0.
Compare the would-change count Preview Only must show 0 package(s) that would change. Actual changed count must equal 0. Stop if actual changed count is not exactly 0.
Approve real apply only after exact match Allowed result is exactly 0/0. Only then type ASSIGN in the existing confirmation field. Do not use any alternative write path or manual database update.
Return to Phase 89 after apply Assignment gaps must reduce to 0 and estimate gaps must remain unchanged. Use the Phase 89 post-apply verification panel after refreshing the Work Packages page. Do not unlock estimate review while assignment gaps remain.

Phase 91 validation checks

  • Phase 90 runbook preserved Phase 91 links back to the Phase 90 manual apply runbook.
  • Phase 89 verification preserved Post-apply verification remains Phase 89.
  • Expected selected count remains stable Expected selected count is 0; current assignment gap count is 0.
  • Expected changed count remains stable Expected changed count is 0; current assignment gap count is 0.
  • ASSIGN confirmation remains mandatory Real assignment must still use the existing ASSIGN-protected bulk assignment form.
  • No new assignment write logic Phase 91 is read-only guidance only and does not create another assignment apply path.
  • No database migration required Phase 91 uses calculated context and template rendering only.
Back to Phase 90 runbook Back to Phase 89 verification

Phase 91 is a read-only readiness gate. It records/reviews operator evidence only, keeps Phase 90 visible, links to Phase 89 verification, preserves Preview Only first, preserves ASSIGN confirmation, and keeps Phase 71 batch-token audit as the official write history.

PHASE90_OPERATOR_ASSIGNMENT_APPLY_RUNBOOK

Phase 90 Safe Operator Assignment Apply Runbook

Assignment closure complete

Assignment gaps are zero. Use Phase 89 verification and continue to Phase 79 estimate review.

Assignment gaps to close 0 Use existing Phase 78 workflow
Expected Preview selected 0 Stop if different
Expected Preview changed 0 Stop if different
Apply confirmation ASSIGN Required by existing form
Assignment gap IDs to preview None
Estimate gap IDs after assignment None
Safety summary Phase 90 is a read-only operator runbook. It does not create a new assignment write path, does not auto-apply assignments, preserves Preview Only first, preserves ASSIGN confirmation, and keeps Phase 71 batch-token audit as the write history path. Phase 90 is read-only guidance only.

Manual apply checklist

Step Action Details Stop rule
1 Open existing safe assignment workflow Use the Phase 78 assignment-gap workflow link. It is prefilled with the current assignment gap package IDs. -
2 Enter the assigned developer Enter the developer or owner in the existing Assigned developer field. Do not change the write path. -
3 Run Preview Only first Preview Only must show 0 selected package(s) and 0 package(s) that would change. Stop if selected/changed counts are not exactly 0/0.
4 Apply only after exact count match Only after Preview Only matches, type ASSIGN and use the existing Apply Bulk Assignment button. Do not apply if the preview is missing packages, changing extra packages, or showing unexpected unchanged records.
5 Refresh and verify in Phase 89 Return to Phase 89 after apply. Assignment gaps must become 0 and estimate gaps must remain unchanged. If assignment gaps remain, do not continue to estimate review.
6 Continue to Phase 79 estimate review only after unlock Phase 79 estimate review unlocks only after assignment gaps are 0. Do not use estimate review as an assignment closure workaround.

Runbook validation checks

Uses existing bulk assignment workflow OK Phase 90 only links to the existing Phase 78/70/71 bulk assignment path.
No new assignment write logic OK This helper prepares read-only runbook context only.
Preview Only required first OK Operator guidance requires Preview Only before any apply action.
Expected selected count carried forward OK Expected selected count is 0.
Expected changed count carried forward OK Expected changed count is 0.
ASSIGN confirmation preserved OK Apply mode remains protected by the existing ASSIGN confirmation field.
Phase 89 verification preserved OK Post-apply verification still routes back to Phase 89.
Estimate review remains locked until assignment closure OK Phase 79 estimate review should unlock only when assignment gaps are zero.
Open Phase 89 verification Open Phase 79 estimate review

Phase 90 adds read-only operator guidance only. It does not add assignment write logic, does not bypass Preview Only, does not bypass ASSIGN, requires no database migration, and preserves Phase 71 batch-token audit behavior.

PHASE89_ASSIGNMENT_APPLY_RESULT_VERIFICATION

Phase 89 Assignment Apply Result Verification / Estimate Review Unlock

Assignment and estimate gaps closed

Assignment and estimate gaps are closed. Continue with final handoff validation and export.

Assignment gaps now 0 Expected after apply: 0
Estimate gaps now 0 Expected unchanged: 0
Current progress 100.0% Expected after assignment: 100.0%
Estimate review unlocked No Unlocked only when assignment gaps are zero
Assignment gaps after apply Expected: 0 | Actual: 0 Real assignment closure is only verified when this count reaches zero.
Estimate gaps unchanged by assignment apply Expected: 0 | Actual: 0 Assignment closure must not silently change estimate review scope.
Progress moved to expected post-assignment value Expected: 100.0% | Actual: 100.0% Expected post-assignment progress is 79.4% while 7 estimate gaps remain.
Latest Phase 71 batch-token audit visible Expected: Visible after real apply | Actual: BA-20260515085904989216 Latest Phase 71 batch-token audit is visible; reversal may be blocked if package state no longer matches the batch.
Estimate review unlock rule Expected: Unlocked only when assignment gaps are 0 | Actual: Fully closed Phase 79 estimate review must stay locked/highlighted only after assignment closure is complete.
Remaining assignment gap IDs None
Remaining estimate gap IDs None
Latest Phase 71 batch token BA-20260515085904989216
Latest Phase 71 changed count 0
Preview final handoff

Phase 89 is read-only. It adds no assignment write logic, preserves Phase 88 guidance, preserves Phase 84 validation, and only highlights Phase 79 estimate review after assignment gaps reach zero.

PHASE88_ACTUAL_ASSIGNMENT_CLOSURE_EXECUTION

Phase 88 Actual Assignment Closure Execution

Read-only execution guide for the real assignment closure step after Phase 87 Preview Only confirmation.

Open existing Preview / Apply workflow
Assignment gaps now 0
Expected Preview selected 0
Expected Preview changed 0
Apply confirmation ASSIGN
Assignment gaps are closed: Continue with estimate gap review or final handoff validation.

Exact assignment gap package IDs: None

Apply safety rules

Rule Status Detail
Preview Only confirmed first OK Operator must record selected=0 and changed=0 before applying.
Stop on Preview Only mismatch OK If the actual Preview Only selected or changed count differs from the expected count, do not apply.
Use existing bulk assignment form only OK Phase 88 is read-only guidance and does not create a new assignment write path.
ASSIGN confirmation remains mandatory OK The existing apply flow must still require the operator to type ASSIGN.
Phase 71 audit trail remains preserved OK Real assignment writes must still create Phase 71 batch-token history through the existing workflow.

Post-apply validation checklist

Check Expected Detail
Assignment gaps after apply 0 Refresh the Work Packages page and confirm the assignment gap count is zero.
Estimate gaps after apply 0 Assignment closure should not change estimate gaps.
Expected progress after assignment closure 100.0% Expected progress gain is 0.0 percentage point(s).
Latest Phase 71 batch audit New batch token visible after real apply The latest Phase 71 batch should show the new assignment batch after apply.
After applying: Assignment gaps are already closed. Validate estimate gaps and continue the final handoff workflow.

Safety: Phase 88 is read-only. It adds execution and post-apply validation guidance only. It does not add assignment write logic, does not bypass Preview Only, does not bypass ASSIGN, requires no database migration, and keeps Phase 71 batch-token history as the audit trail.

PHASE87_ASSIGNMENT_PREVIEW_RESULT_CAPTURE

Phase 87 Assignment Preview Result Capture

Read-only operator capture guide for recording the actual Preview Only result before any real assignment.

Open Preview Only workflow
Expected selected 0
Expected changed 0
Assignment gap IDs
Operator confirmation rule: Stop and do not apply if the actual Preview Only selected count or changed count does not match the expected Phase 86 values.
Proceed rule: Proceed to the existing Apply Bulk Assignment path only when the actual Preview Only selected count and changed count match the expected values, and then type ASSIGN.

Preview result capture checklist

Field to record Expected value Guidance
Actual Preview Only selected count 0 Record the selected count shown by Preview Only. It must be 0.
Actual Preview Only changed count 0 Record the would-change count shown by Preview Only. It must be 0.
Operator note Counts match / counts do not match Capture a short note before applying, especially if the counts do not match.

Safety validation

Check Status Detail
Phase 86 expected selected count reused Review Expected selected count is 0.
Phase 86 expected changed count reused Review Expected changed count is 0.
Operator must stop on mismatch OK Stop and do not apply if the actual Preview Only selected count or changed count does not match the expected Phase 86 values.
ASSIGN confirmation remains required OK Real assignment remains protected by the existing ASSIGN confirmation.
Existing bulk assignment workflow remains the write path OK Phase 87 is read-only guidance and does not create a new assignment write path.
Phase 71 audit safety preserved OK Assignment writes must still create/keep Phase 71 batch-token history.

Safety: Phase 87 is read-only. It captures operator guidance only, adds no assignment write logic, requires no database migration, and keeps Preview Only, ASSIGN confirmation, and Phase 71 batch-token history intact.

PHASE86_ASSIGNMENT_CLOSURE_PREVIEW_READINESS

Phase 86 Assignment Closure Preview Readiness

Read-only operator checklist for capturing and validating the Preview Only result before real assignment.

0 Assignment gaps to preview
0 Expected selected count
0 Expected changed count
ASSIGN Apply confirmation still required
No assignment preview required

All assignment gaps are already closed. Continue with estimate review or final handoff validation.

Expected Preview Only result: Preview Only should show 0 selected package(s) and 0 package(s) that would change.

Assignment gap package IDs: None

Readiness check Status Detail
Phase 85 simulation is available OK The Phase 85 simulation must remain visible so the operator can compare expected assignment closure results.
Preview Only is the first required action OK The existing safe bulk assignment workflow must be used in Preview Only mode before any write.
Expected selected count is known OK Preview Only should select 0 package(s).
Expected changed count is known OK If one developer is assigned to all selected gaps, Preview Only should show 0 package(s) that would change.
ASSIGN confirmation is preserved OK Apply mode must still require the operator to type ASSIGN.
Phase 71 audit/reversal safety is preserved OK Real assignment must still create Phase 71 batch-token history through the existing write path.

Apply warning: Do not apply the assignment unless the Preview Only selected count and changed count match the expected values.

Safety: Phase 86 is read-only. It adds preview-readiness guidance only and does not add assignment write logic. Assignment writes remain protected by Preview Only, ASSIGN confirmation, and Phase 71 batch-token history.

Open Preview Only workflow
PHASE84_POST_ASSIGNMENT_VALIDATION

Phase 84 Post-Assignment Progress Validation

Validates assignment closure progress after the Phase 83 guided assignment workflow, using existing Phase 82/83 calculations and the Phase 71 batch-token audit trail.

100.0% Current closure progress
0 Assignment gaps remaining
0 Estimate gaps remaining
Yes Latest Phase 71 batch visible
Assignment and estimate gaps closed

All assignment and estimate gaps are closed. Continue with final handoff preview and export.

Validate assignment progress

17 of 17 packages currently have assigned developers.

Review latest Phase 71 batch

Latest Phase 71 batch is visible but reversal is blocked because package state no longer matches the batch.

Move to estimate review

Unlocked when assignment gaps reach zero.

Remaining assignment package IDs: None

Remaining estimate package IDs: None

Latest Phase 71 batch: BA-20260515085904989216 · changed packages: 0 · reversible: No

Preview final handoff pack

Safety: Phase 84 adds validation and guidance only. It does not add assignment write logic. Assignment writes remain protected by Preview Only, ASSIGN confirmation, and Phase 71 batch-token history.

PHASE83_GUIDED_ASSIGNMENT_CLOSURE_PANEL

Phase 83 Guided Assignment Gap Closure

Guided project-lead workflow for closing the remaining developer assignment gaps through the existing safe Phase 78/70/71 bulk assignment path. No new write logic is used here.

0 Assignment gaps to close
100.0% Current gap closure progress
ASSIGN Required apply confirmation
All assignment gaps closed

Continue to the estimate gap review workflow.

Exact assignment gap package IDs: None

Recommended action: No developer assignment action required. Keep Preview Only as the first action. Apply mode remains protected by the existing ASSIGN confirmation and Phase 71 batch-token audit/reversal safety.

Continue to estimate review

Safe closure checklist

Step Status Detail
Open the guided assignment closure page Ready / preserved The page is prefilled with the exact remaining assignment gap package IDs.
Run Preview Only first Ready / preserved Preview Only must show the selected packages before any write action is applied.
Apply only after typing ASSIGN Ready / preserved The existing bulk assignment view enforces ASSIGN before Apply Bulk Assignment.
Preserve Phase 71 audit and reversal safety Ready / preserved No new write logic is introduced; existing Phase 71 batch-token history remains the write path.
No remaining assignment gaps. Continue with estimate gap review and final handoff verification.
PHASE82_GAP_CLOSURE_EXECUTION_PANEL

Phase 82 Automated Gap Closure Execution

Project-lead execution panel for safely closing the remaining assignment and estimate gaps through the existing Phase 78/79 workflows while preserving the Phase 81 audit trail.

100.0% Gap closure progress
0 Assignment gaps remaining
0 Estimate gaps remaining
10 Recent audit entries
Automated gap closure complete

Review the final handoff preview, then export the developer handoff CSV.

Close developer assignment gaps

0 item(s) remaining.

Open safe assignment closure
Close estimate gaps

0 item(s) remaining.

Open estimate review closure
Verify final handoff pack

0 item(s) remaining.

Preview final handoff pack

Assignment gap package IDs: None

Estimate gap package IDs: None

Preview final handoff pack Export final developer handoff CSV

Phase 81 audit trail preserved

Assignment history rows: 13 · Estimate history rows: 7 · Final closure history rows: 0

Package Assignment Estimate Changed by Note
#8 Manifest parsed successfully ERPWeb Developer → ERPWeb Developer 0.00h → 0.50h ERPWeb Developer Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment c…
#7 Manifest parsed successfully ERPWeb Developer → ERPWeb Developer 0.00h → 0.50h ERPWeb Developer Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment c…
#6 Manifest metadata captured ERPWeb Developer → ERPWeb Developer 0.00h → 0.50h ERPWeb Developer Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment c…
#5 Dependencies detected ERPWeb Developer → ERPWeb Developer 0.00h → 0.50h ERPWeb Developer Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment c…
#4 Dependencies detected ERPWeb Developer → ERPWeb Developer 0.00h → 0.50h ERPWeb Developer Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment c…
#3 Structured dependency records rebuilt ERPWeb Developer → ERPWeb Developer 0.00h → 0.50h ERPWeb Developer Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment c…
#2 Dependencies captured ERPWeb Developer → ERPWeb Developer 0.00h → 0.50h ERPWeb Developer Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment c…
#17 Dependency upgrade recommendation: sale Unassigned → ERPWeb Developer 0.50h → 0.50h Johan Jordaan Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment…
#16 Dependency upgrade recommendation: base Unassigned → ERPWeb Developer 0.50h → 0.50h Johan Jordaan Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment…
#8 Manifest parsed successfully Unassigned → ERPWeb Developer 0.00h → 0.00h Johan Jordaan Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment…
Phase 81 Final Handoff Action Execution / Gap Closure Audit Trail

Phase 81 Final Handoff Action Execution

Project-lead execution view for closing assignment and estimate gaps while preserving the existing work package history audit trail.

100.0% Gap closure progress
0 Assignment gaps remaining
0 Estimate gaps remaining
20 Recent audit rows
Ready for final export

Review the final handoff preview, then export the developer handoff CSV.

Done

Assign missing developers

Done

Review and update missing estimates

Done

Confirm final handoff readiness

Assignment gap package IDs: None

Estimate gap package IDs: None

Preview final handoff pack Export final developer handoff CSV

Recent closure audit trail

When Package Action Assignment Estimate Changed by Note
2026-05-15 11:53 #8 — Manifest parsed successfully Estimate ERPWeb Developer → ERPWeb Developer 0.00h → 0.50h ERPWeb Developer Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment c…
2026-05-15 11:52 #7 — Manifest parsed successfully Estimate ERPWeb Developer → ERPWeb Developer 0.00h → 0.50h ERPWeb Developer Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment c…
2026-05-15 11:52 #6 — Manifest metadata captured Estimate ERPWeb Developer → ERPWeb Developer 0.00h → 0.50h ERPWeb Developer Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment c…
2026-05-15 11:52 #5 — Dependencies detected Estimate ERPWeb Developer → ERPWeb Developer 0.00h → 0.50h ERPWeb Developer Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment c…
2026-05-15 11:51 #4 — Dependencies detected Estimate ERPWeb Developer → ERPWeb Developer 0.00h → 0.50h ERPWeb Developer Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment c…
2026-05-15 11:51 #3 — Structured dependency records rebuilt Estimate ERPWeb Developer → ERPWeb Developer 0.00h → 0.50h ERPWeb Developer Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment c…
2026-05-15 11:50 #2 — Dependencies captured Estimate ERPWeb Developer → ERPWeb Developer 0.00h → 0.50h ERPWeb Developer Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment c…
2026-05-15 10:59 #17 — Dependency upgrade recommendation: sale Assignment Unassigned → ERPWeb Developer 0.50h → 0.50h Johan Jordaan Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment…
2026-05-15 10:59 #16 — Dependency upgrade recommendation: base Assignment Unassigned → ERPWeb Developer 0.50h → 0.50h Johan Jordaan Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment…
2026-05-15 10:59 #8 — Manifest parsed successfully Assignment Unassigned → ERPWeb Developer 0.00h → 0.00h Johan Jordaan Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment…
Phase 78 Developer Assignment Readiness Workflow

Estimate gap review

You came here from the Phase 78 readiness workflow. The bulk assignment form below has been prefilled where possible so the project lead can preview or apply the fix safely.

package_ids Prefilled mode
- Package IDs
Phase 90 post-assignment follow-up: review remaining estimate gaps. Suggested note
Phase 79 Assignment Gap Resolution Hardening / Estimate Gap Review Workflow

Phase 79 Estimate Gap Review

Review each package below, enter a realistic estimate in the existing Estimated hours field, add a note, then click Save Tracking.

0 Selected estimate gaps
0 Total estimate gaps
None Package IDs to review
No selected estimate gaps found for this Phase 79 review focus.
Phase 73 Developer Handoff Export
Phase 74 Developer Handoff Export Refinement Phase 75 Developer Handoff Pack Preview

Preview the Phase 75 handoff landing page before downloading the developer-ready CSV pack, or use the filtered preview links below for assignment-ready groups, high-impact handoffs, explicit package IDs, and assigned developer packs.

Download Developer Handoff Pack CSV Download Full Developer Handoff Pack CSV Export Assignment-Needed Only

Phase 75 preview counts: full pack 17 package(s); assignment-needed 0 package(s); high-impact 0 package(s).

Phase 72 Developer Assignment Handoff

Controlled handoff view for real assignments: use the recommended filters, suggested developer names, and package ID groups below before applying bulk assignment. This uses existing work package and history fields only.

0 Ready for developer assignment
0h unassigned
0 High-impact unassigned
0h high-impact
17 Already assigned / active
0 ready to close · 0 blocked
All work packages currently have a developer assignment. Use the owner summary and closure queue to track progress.

Recommended assignment filters

No assignment filter recommendations are currently needed.

Suggested developer names

ERPWeb Developer

Existing active assignment owner · assignment history, current package assignment

Current packages: 17 Open: 17 History: 24 23.50h Preview developer pack
phase70_test_developer

Previously used assignment owner · assignment history

Current packages: 0 Open: 0 History: 16 0h Preview developer pack
phase71_test_developer

Previously used assignment owner · assignment history

Current packages: 0 Open: 0 History: 12 0h Preview developer pack
Phase65 Verification Developer

Previously used assignment owner · assignment history

Current packages: 0 Open: 0 History: 1 0h Preview developer pack
Phase9 Test Developer

Previously used assignment owner · assignment history

Current packages: 0 Open: 0 History: 1 0h Preview developer pack

Bulk Developer Assignment

Assign multiple work packages at once using safe filters. This updates only the existing assigned developer field and writes history entries for each changed package.

Safety: use Preview Only first to see how many packages would change. Apply mode requires ASSIGN, unchanged packages are skipped, every changed package gets a tracking history entry, and Phase 71 adds a batch token to future bulk assignment history notes for safer audit/reversal.

Recent Bulk Assignment Audit & Reversal Safety

Phase 71 tracks future bulk assignment batches using history-note batch tokens. The latest tokened batch can be reversed only when the package still has the assignment created by that batch.

Latest Phase 71 batch: BA-20260515085904989216 · Total: 17 · Reversible: 17 · Blocked/skipped: 0

Recent assignment history

When Package Old owner New owner Changed by Batch
2026-05-15 10:59 #17 — Dependency upgrade recommendation: sale Unassigned ERPWeb Developer Johan Jordaan BA-20260515085904989216
2026-05-15 10:59 #16 — Dependency upgrade recommendation: base Unassigned ERPWeb Developer Johan Jordaan BA-20260515085904989216
2026-05-15 10:59 #8 — Manifest parsed successfully Unassigned ERPWeb Developer Johan Jordaan BA-20260515085904989216
2026-05-15 10:59 #7 — Manifest parsed successfully Unassigned ERPWeb Developer Johan Jordaan BA-20260515085904989216
2026-05-15 10:59 #6 — Manifest metadata captured Unassigned ERPWeb Developer Johan Jordaan BA-20260515085904989216
2026-05-15 10:59 #5 — Dependencies detected Unassigned ERPWeb Developer Johan Jordaan BA-20260515085904989216
2026-05-15 10:59 #4 — Dependencies detected Unassigned ERPWeb Developer Johan Jordaan BA-20260515085904989216
2026-05-15 10:59 #3 — Structured dependency records rebuilt Unassigned ERPWeb Developer Johan Jordaan BA-20260515085904989216
2026-05-15 10:59 #2 — Dependencies captured Unassigned ERPWeb Developer Johan Jordaan BA-20260515085904989216
2026-05-15 10:59 #9 — Manifest version does not start with source Odoo major version Unassigned ERPWeb Developer Johan Jordaan BA-20260515085904989216
2026-05-15 10:59 #13 — Legacy states usage detected Unassigned ERPWeb Developer Johan Jordaan BA-20260515085904989216
2026-05-15 10:59 #14 — Legacy attrs usage detected Unassigned ERPWeb Developer Johan Jordaan BA-20260515085904989216

Top Assignment / Closure Queue Items

Queue Stage Owner Priority Status Package Next action
Assigned / Not Started ERPWeb Developer Critical To Do #15 — Developer upgrade review: erpweb_phase3_risky_test_module Start the package, capture progress notes, and move it toward Review.
Assigned / Not Started ERPWeb Developer High To Do #1 — Old Odoo API method signature detected Start the package, capture progress notes, and move it toward Review.
Assigned / Not Started ERPWeb Developer Medium To Do #12 — Deprecated @api.multi usage Start the package, capture progress notes, and move it toward Review.
Assigned / Not Started ERPWeb Developer Medium To Do #14 — Legacy attrs usage detected Start the package, capture progress notes, and move it toward Review.
Assigned / Not Started ERPWeb Developer Medium To Do #10 — Legacy Odoo JavaScript module pattern detected Start the package, capture progress notes, and move it toward Review.
Assigned / Not Started ERPWeb Developer Medium To Do #13 — Legacy states usage detected Start the package, capture progress notes, and move it toward Review.
Assigned / Not Started ERPWeb Developer Medium To Do #11 — Legacy web.* JavaScript require detected Start the package, capture progress notes, and move it toward Review.
Assigned / Not Started ERPWeb Developer Low To Do #9 — Manifest version does not start with source Odoo major version Start the package, capture progress notes, and move it toward Review.
Assigned / Not Started ERPWeb Developer Info To Do #2 — Dependencies captured Start the package, capture progress notes, and move it toward Review.
Assigned / Not Started ERPWeb Developer Info To Do #4 — Dependencies detected Start the package, capture progress notes, and move it toward Review.
Assigned / Not Started ERPWeb Developer Info To Do #5 — Dependencies detected Start the package, capture progress notes, and move it toward Review.
Assigned / Not Started ERPWeb Developer Info To Do #6 — Manifest metadata captured Start the package, capture progress notes, and move it toward Review.

Developer / Owner Load Summary

ERPWeb Developer

Total: 17 · Open: 17 · High-impact: 2 · 23.50h

Ready to close: 0 Blocked: 0

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
0 Missing developer assignment
0 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.
  • 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.
  • Record the developer decision, target-version test result, and proof/reference.
  • Prioritise review evidence before lower-risk closure work.
#1 — Old Odoo API method signature detected High To Do Not Ready
  • Package has not started yet.
  • 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.
  • Record the developer decision, target-version test result, and proof/reference.
  • Prioritise review evidence before lower-risk closure work.
#10 — Legacy Odoo JavaScript module pattern detected Medium To Do Not Ready
  • Package has not started yet.
  • Manual-review package is not yet in Review or Done.
  • 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.
  • 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.
  • Manual-review package is not yet in Review or Done.
  • 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.
  • 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.
  • Manual-review package is not yet in Review or Done.
  • 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.
  • 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.
  • Manual-review package is not yet in Review or Done.
  • 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.
  • 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.
  • Manual-review package is not yet in Review or Done.
  • 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.
  • 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.
  • Manual-review package is not yet in Review or Done.
  • 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.
  • Record the developer decision, target-version test result, and proof/reference.
#2 — Dependencies captured Info To Do Not Ready
  • Package has not started yet.
  • Manual-review package is not yet in Review or Done.
  • 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.
  • 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.
  • Manual-review package is not yet in Review or Done.
  • 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.
  • 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
23.50 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 23.50h
Seq 20 Critical Module Review To Do 6.00h erpweb_phase3_risky_test_module Score 299 Manual Review Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#15 — Developer upgrade review: erpweb_phase3_risky_test_module

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • 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.
  • 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: todo → todo · Assigned: - → ERPWeb Developer · Hours: 6.00 → 6.00
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan
Status: todo → todo · Assigned: phase71_test_developer → - · Hours: 6.00 → 6.00
Evidence / change note: Phase 71 verification reset: restored assignment after tokened batch test BA-20260514120341005730.
May 14, 2026, 2:03 p.m. · Changed by phase71_status
Status: todo → todo · Assigned: - → phase71_test_developer · Hours: 6.00 → 6.00
Evidence / change note: Phase 71 bulk assignment batch: BA-20260514120341005730. Phase 71 status command positive assignment test.
May 14, 2026, 2:03 p.m. · Changed by phase71_status

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 Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#1 — Old Odoo API method signature detected

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • 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.
  • 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:30 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:24 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:16 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: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: todo → todo · Assigned: - → ERPWeb Developer · Hours: 2.00 → 2.00
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan
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:30 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:30 p.m.

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 Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#10 — Legacy Odoo JavaScript module pattern detected

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • Manual-review package is not yet in Review or Done.

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.
  • Record the developer decision, target-version test result, 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.

Latest tracking history

Status: todo → todo · Assigned: - → ERPWeb Developer · Hours: 2.00 → 2.00
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan

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 Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#11 — Legacy web.* JavaScript require detected

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • Manual-review package is not yet in Review or Done.

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.
  • Record the developer decision, target-version test result, 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.

Latest tracking history

Status: todo → todo · Assigned: - → ERPWeb Developer · Hours: 2.00 → 2.00
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan

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 Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#12 — Deprecated @api.multi usage

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • Manual-review package is not yet in Review or Done.

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.
  • Record the developer decision, target-version test result, 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.

Latest tracking history

Status: todo → todo · Assigned: - → ERPWeb Developer · Hours: 2.00 → 2.00
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan

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 Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#14 — Legacy attrs usage detected

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • Manual-review package is not yet in Review or Done.

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.
  • Record the developer decision, target-version test result, 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.

Latest tracking history

Status: todo → todo · Assigned: - → ERPWeb Developer · Hours: 2.00 → 2.00
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan

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 Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#13 — Legacy states usage detected

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • Manual-review package is not yet in Review or Done.

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.
  • Record the developer decision, target-version test result, 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.

Latest tracking history

Status: todo → todo · Assigned: - → ERPWeb Developer · Hours: 2.00 → 2.00
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan

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 Assigned: ERPWeb Developer Not Ready Assigned / Not Started

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

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • Manual-review package is not yet in Review or Done.

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.
  • Record the developer decision, target-version test result, 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.

Latest tracking history

Status: todo → todo · Assigned: - → ERPWeb Developer · Hours: 1.00 → 1.00
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan

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.50h erpweb_phase3_risky_test_module Dependency Review Manual Review Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#2 — Dependencies captured

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • Manual-review package is not yet in Review or Done.

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.
  • Record the developer decision, target-version test result, 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.

Latest tracking history

Status: todo → todo · Assigned: ERPWeb Developer → ERPWeb Developer · Hours: - → 0.50
Evidence / change note: Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment closure.
May 15, 2026, 11:50 a.m. · Changed by ERPWeb Developer
Status: todo → todo · Assigned: - → ERPWeb Developer · Hours: - → -
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan

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.50h erpweb_phase3_risky_test_module Dependency Review Manual Review Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#3 — Structured dependency records rebuilt

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • Manual-review package is not yet in Review or Done.

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.
  • Record the developer decision, target-version test result, 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.

Latest tracking history

Status: todo → todo · Assigned: ERPWeb Developer → ERPWeb Developer · Hours: - → 0.50
Evidence / change note: Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment closure.
May 15, 2026, 11:51 a.m. · Changed by ERPWeb Developer
Status: todo → todo · Assigned: - → ERPWeb Developer · Hours: - → -
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan

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.50h erpweb_phase3_risky_test_module Dependency Review Manual Review Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#4 — Dependencies detected

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • Manual-review package is not yet in Review or Done.

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.
  • Record the developer decision, target-version test result, 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.

Latest tracking history

Status: todo → todo · Assigned: ERPWeb Developer → ERPWeb Developer · Hours: - → 0.50
Evidence / change note: Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment closure.
May 15, 2026, 11:51 a.m. · Changed by ERPWeb Developer
Status: todo → todo · Assigned: - → ERPWeb Developer · Hours: - → -
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan

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.50h erpweb_phase3_risky_test_module Dependency Review Manual Review Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#5 — Dependencies detected

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • Manual-review package is not yet in Review or Done.

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.
  • Record the developer decision, target-version test result, 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.

Latest tracking history

Status: todo → todo · Assigned: ERPWeb Developer → ERPWeb Developer · Hours: - → 0.50
Evidence / change note: Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment closure.
May 15, 2026, 11:52 a.m. · Changed by ERPWeb Developer
Status: todo → todo · Assigned: - → ERPWeb Developer · Hours: - → -
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan

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.50h erpweb_phase3_risky_test_module Validate Manifest Metadata Manual Review Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#6 — Manifest metadata captured

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • Manual-review package is not yet in Review or Done.

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.
  • Record the developer decision, target-version test result, 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.

Latest tracking history

Status: todo → todo · Assigned: ERPWeb Developer → ERPWeb Developer · Hours: - → 0.50
Evidence / change note: Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment closure.
May 15, 2026, 11:52 a.m. · Changed by ERPWeb Developer
Status: todo → todo · Assigned: - → ERPWeb Developer · Hours: - → -
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan

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.50h erpweb_phase3_risky_test_module Validate Manifest Metadata Manual Review Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#7 — Manifest parsed successfully

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • Manual-review package is not yet in Review or Done.

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.
  • Record the developer decision, target-version test result, 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.

Latest tracking history

Status: todo → todo · Assigned: ERPWeb Developer → ERPWeb Developer · Hours: - → 0.50
Evidence / change note: Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment closure.
May 15, 2026, 11:52 a.m. · Changed by ERPWeb Developer
Status: todo → todo · Assigned: - → ERPWeb Developer · Hours: - → -
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan

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.50h erpweb_phase3_risky_test_module Validate Manifest Metadata Manual Review Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#8 — Manifest parsed successfully

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started yet.
  • Manual-review package is not yet in Review or Done.

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.
  • Record the developer decision, target-version test result, 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.

Latest tracking history

Status: todo → todo · Assigned: ERPWeb Developer → ERPWeb Developer · Hours: - → 0.50
Evidence / change note: Phase 97 manual estimate gap closure: realistic estimate added using existing tracking form after Phase 96 assignment closure.
May 15, 2026, 11:53 a.m. · Changed by ERPWeb Developer
Status: todo → todo · Assigned: - → ERPWeb Developer · Hours: - → -
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan

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 Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#16 — Dependency upgrade recommendation: base

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started 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.
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.

Latest tracking history

Status: todo → todo · Assigned: - → ERPWeb Developer · Hours: 0.50 → 0.50
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan

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 Assigned: ERPWeb Developer Not Ready Assigned / Not Started

#17 — Dependency upgrade recommendation: sale

Assignment / closure queue: Assigned / Not Started

Next project-lead action: Start the package, capture progress notes, and move it toward Review.

Closure readiness: Not Ready

Why not ready:

  • Package has not started 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.
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.

Latest tracking history

Status: todo → todo · Assigned: - → ERPWeb Developer · Hours: 0.50 → 0.50
Evidence / change note: Phase 71 bulk assignment batch: BA-20260515085904989216. Phase 96 controlled manual apply: preview remaining assignment gaps first.
May 15, 2026, 10:59 a.m. · Changed by Johan Jordaan

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 2.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 1.50h
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.