Statuses (name, colour, counts toward hours, order) are set up on the plugin's settings page
instead of being hard-coded. Appointments keep a fixed key, so renaming is safe; removing a status
in use asks which status to move its appointments to (done on save by a SettingsController hook).
Colours come from the settings everywhere statuses show, which also fixes Cancelled never being
coloured (cancelled/canceled mismatch).
Call-outs (an employee off work) are their own kind of entry (event_type 'call_out') with an
employee, date, days and notes, added from a button on each calendar day. They sit at the top of
the day in red stripes and never count toward hours. Migration 004 converts Call_Out appointments.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- An appointment's hours can't be less than its estimate's labor hours
(checked when the estimate or hours change, so the quick status buttons
still work on older appointments). Picking an estimate on the form, or
arriving from an estimate page, raises the hours to match.
- The appointment page lists the issues linked to its estimate.
- Creating issues from an estimate moved to redmine_qbo_billing (now
required): Create Issues from Estimate opens its page with this
appointment's dates, technician, vehicle and project (via
qbo_billing_issue_defaults). The builder, preview page, settings and rake
task are removed here; the old settings stay registered so billing can
read them until its own are saved.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BiwYMjhoQvL7XsKKfRz4pM
Redmine has no default-project setting for new issues, so the preview
page used the first project the user could add issues to whenever an
appointment had no project. The plugin settings now have a Default
project; the order is: project chosen on the page, the appointment's
project, the default project, then the first allowed project.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BiwYMjhoQvL7XsKKfRz4pM
- "Create Issues from Estimate" now opens a preview listing each
matching estimate line: include checkbox, subject (from the line
description), tracker dropdown, template dropdown and estimated
hours (from the line quantity)
- Admins set which QBO item codes to look for (e.g. Labor, Alignments)
and a default tracker in the plugin settings
- Optional redmine_issue_templates support: templates supply the issue
description; titles still come from the line description
- New appointment_estimate_issues table records which issue came from
which estimate line, so a line can't be turned into an issue twice;
deleting the issue frees the line again
- Creation is all-or-nothing; errors are shown on the preview page
- Removes the old Labor-only create_issues_from_labor_lines code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BiwYMjhoQvL7XsKKfRz4pM
- customer_options is now covered by the add/edit permissions, so
non-admin staff get the vehicle/estimate dropdowns
- create_issues is now a POST member route with its own permission,
checks add_issues on the target project, no longer redirects to a
missing route, and has a button on the appointment page
- "Last" week-of-month holidays (e.g. Memorial Day) now match every year
- Cancelled and Call Out appointments no longer count toward hours
- Calendar only shows appointments to users with View customer
appointments, and only loads those near the displayed month
- due_date skips weekends and holidays, matching the calendar layout
- Subjects keep their casing; only the first letter is capitalized
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BiwYMjhoQvL7XsKKfRz4pM
Adds a history page listing past customer appointments with customer,
status and date-range filters and pagination, linked from the customer
page, the appointments index and each appointment.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BiwYMjhoQvL7XsKKfRz4pM
- Implement HolidaysController for managing holidays
- Create Holiday model with validation for recurrence types
- Add holiday form and views for creating, editing, and listing holidays
- Integrate holiday checks into customer appointment scheduling
- Update locale file for holiday-related labels and error messages
- Add migration for holidays table
- Update plugin version and add holidays to admin menu