Own the QuickBooks VIN and Mileage fields

redmine_qbo now handles QuickBooks custom fields generically; this plugin claims the fields named like
VIN and Mileage (Vehicles::QboFields) and supplies their behaviour:

- qbo_billing_issue_values keyed by field id; qbo_billing_field_options (the customer's vehicles for the
  VIN box) and qbo_billing_field_defaults (the work orders' VIN and highest mileage) replace the VIN hooks.
- Editor script (view_qbo_estimate_form_bottom): VINs in capitals; importing time or estimates fills the
  VIN from the work orders' vehicle (or an estimate's own VIN), warns about several vehicles, and fills
  the highest mileage. The several-vehicle and missing-VIN-field texts moved here.
- qbo_calendar_appointment_params: an appointment added from an estimate gets the vehicle with its VIN.
- The estimate's VIN is read through redmine_qbo's generic custom_field_value.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BiwYMjhoQvL7XsKKfRz4pM
This commit is contained in:
Claude committed 2026-10-31 11:34:28 -04:00
1 parent 1aa2fa9d5e
commit 70f4ce7e4a
7 files changed
+150 -19

No files matched your search

+2
View File
@@ -34,6 +34,8 @@ en:
label_search_vehicles: "Search Vehicles"
label_unknown: "Unknown"
label_vehicle: "Vehicle"
text_invoice_many_vehicles: "These work orders are for more than one vehicle:"
text_no_vin_field: "QuickBooks isn't sharing a text custom field named VIN, so VINs can't be filled in."
text_estimate_vehicle_matched: "Matches the estimate's VIN (%{vin})."
text_estimate_vehicle_unmatched: "None of the customer's vehicles has the estimate's VIN (%{vin}). Pick the vehicle for these issues, or add it to the customer first."
text_estimate_vehicle_no_vin: "The estimate has no VIN. Pick the vehicle for these issues."