Appointment statuses in the plugin settings; call-outs as their own entry

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>
This commit is contained in:
rickyandClaude Opus 5.5 committed 2026-11-02 20:22:52 -05:00
1 parent f2a16b1821
commit 31356ac3fb
23 files changed
+536 -252

No files matched your search

@@ -66,8 +66,7 @@
<tbody>
<% expanded_appointments.each do |item| %>
<% appt = item[:appointment] %>
<% status_slug = appt.status.to_s.parameterize %>
<tr class="<%= cycle('odd', 'even') %> appointment-row status-<%= status_slug %>">
<tr class="<%= cycle('odd', 'even') %> appointment-row">
<td class="subject">
<%= link_to appt.subject, customer_appointment_path(appt) %>
<% if item[:total_days] > 1 %>
@@ -84,11 +83,7 @@
<%= format_date(item[:date]) %>
</td>
<td class="status">
<% if appt.status.present? %>
<span class="badge status-badge status-<%= status_slug %>">
<%= appt.status.to_s.humanize %>
</span>
<% end %>
<%= appointment_status_badge(appt, css: 'badge status-badge') %>
</td>
</tr>
<% end %>