Warp
← Warp Shift questions

Warp Shift changelog

Update with composer update qalainau/filament-warp-shift, then run php artisan filament:assets.

1.6.1 Nov 20, 2026

Fixed

  • Console error warpShiftRoster is not defined: on pages where Livewire re-renders the component inside another Alpine component, the browser console could show warpShiftRoster is not defined before the component's script had arrived. Empty components are now registered up front, and the real ones replace them as soon as they load. No visible change.
  • Copying cells: a cell whose text contains a lone carriage return (\r, e.g. text that came from an old Mac file) is now quoted when copied, so pasting it into Excel or Google Sheets no longer splits it into extra rows.

1.6.0 Nov 15, 2026

Added

  • The shift codes list also asks your app's policy (viewAny) when you have one for the model, together with canManage().
  • Restricting pages per role. canAccessUsing(fn (User $user, string $page): bool => …) and canWriteUsing(…) on the plugin let your app decide who can open each roster, My shifts and Requests & swaps (menu, URL and Livewire calls), and who only looks at them. They work together with canManage. A roster page can also override canWrite() to be read-only. Without them nothing changes.

Fixed

  • My shifts no longer fails in apps that use Model::preventLazyLoading() or Model::shouldBeStrict() when someone has asked you to swap a shift or offered one (the roster of each swap is now loaded with the list).

1.5.2 Nov 12, 2026

Changed

  • Now requires Filament 5.8.3 or later (was 5.0). Older 5.x versions have known security advisories (Composer 2.9 and later refuses to install them), and the plugin cannot be tested on them. The tests now also run on the lowest supported versions before each release.

1.5.1 Nov 11, 2026

Fixed

  • useWarpDatePicker(companyDaysOff: true) now reads the company days off of the roster's tenant (asTenant(), RosterEvaluation::tenant(), the other tenant() methods, or tenantKey()), not the current panel's tenant. A roster read from a staff panel without tenancy, a command or a queued job missed the company days off (the year-end break), so the holidays there differed from the manager's screen. Needs Warp DatePicker 1.0.0 or later.

1.5.0 Nov 10, 2026

Added

  • useWarpDatePicker(): the holidays of the roster come from a Warp DatePicker calendar (the panel's or one place's), optionally with company days off. Warp DatePicker is not released yet; nothing changes until you call it.
  • A Marks legend under the roster explains every mark: rule breaks (red and amber), the dot by a date, a name or "Staff", requests (approved, waiting and "not this shift" side by side), notes, pins, unsaved and changed-since-published cells (and today's clock-in, places, unavailable days and app-set staff needed when the roster uses them).

Changed

  • Shift codes: the "In use" column and toggle is now called Active. A code that a roster uses shows a grayed-out Delete with the reason in a tooltip, instead of no Delete at all.

Fixed

  • The totals' short headings (Days, Off, Hrs, OT, Hol., Night, Wknd and the code counts) spell themselves out when you point at them: "Wknd" says "Weekend days worked: Saturdays, Sundays and holidays with a work shift".
  • On a narrow screen the day columns are cut off at the right edge with nothing to say they scroll. A shadow at the right edge now shows more days to the right, and one next to the names shows days hidden to the left.
  • When the roster is taller than the window, the staff needed rows at the bottom looked like they covered the last staff row. A shadow above them now shows the rows continue underneath while there is more to scroll.
  • My shifts: on a Sunday, today's number was red on the green circle. It is white now.
  • The roster no longer jumps up and down while you work. The status bar above it used to grow to two lines and shrink back as the save status ("Not saved yet", "Saving…", "All changes saved") and short messages changed length, so a click right after typing could land on the next person's row. The status bar now keeps one height: the status, rule count, labour cost and clock-in notice stay on one line (cut with "…" when there is no room, full text on hover and for screen readers), and messages appear on a line below that is always kept free. On a phone the labour cost and the clock-in notice get lines of their own.

1.4.0 Nov 7, 2026

Added

  • Rule code keys are checked. When a rule, codes([...]) or rotations() names a shift code key that no code has, the rule used to check nothing without a word. Now, each time a roster is read (the page, RosterEvaluation, auto-fill), against the current tenant's codes: a key that is another code's label (AfterShift::make('N') for the code with the key night) throws an InvalidArgumentException outside production that names the key, the rules that use it and the right key; a key that matches no code (a typo, or a code this tenant has not created yet) is logged as a warning, once per request. In production both are only logged. Roster::strictCodes() makes every unknown key throw (also in production), strictCodes(false) only logs. Nothing is checked before any code exists. See "Keys that no code has" in the README.

Changed

  • README, Boost guideline and skill: an example where the code typed in the cells and its key differ (N and night), and that rules take the key. staffForUser() is in the guideline and in the skill's setup steps: when the staff model is not User, My shifts otherwise takes the User as the staff record and shows an empty calendar.

1.3.0 Nov 6, 2026

Added

  • RosterEvaluation::forDay($date) and forTeam(): the rule breaks of a day (RequiredSkill) and of the whole roster (AverageNightHours, TeamMaxHours, budget), with the same keys as a person's violations plus scope, so tests and dashboards can check them from PHP.
  • A JavaScript API for browser tests on the roster's Alpine component (.fi-warp-sft-roster): cellPoint({ staff, date }) (where to click a cell, scrolled into view), shiftsOnScreen(filter) (the cells with a code as drawn: code, label, times, rule-break mark, position) and whenIdle() (waits until saved and drawn). See "Browser tests (JavaScript)" in the README.

Fixed

  • Rule messages say one in the singular: "1 day of leave", "1 day off", "N 1 time", "for 1 person" (was "1 days", "1 times", "1 people"), in every language with plurals (French also for 0). "Together" now reads "Partners on the same N: 0 (needs 1)" instead of "Needs 2 partner …".
  • RosterEvaluation with clock-ins: a past scheduled day without a clock-in no longer makes the person's row count as unfinished, so MinLeaveDays (also with yearFrom()), MinDaysOff, MinHours and MinCount still warn. The day counts as filled in, and as a day off for MinDaysOff.

1.2.0 Nov 6, 2026

Added

  • JapaneseHolidays::for($year): the Japanese holidays of a year as a list of dates.

Changed

  • README: a "Testing" section: a feature test of a rule with RosterPlan and RosterEvaluation, and what cannot be tested from PHP yet. RosterEvaluation returns the breaks of each person only; RequiredSkill, staff needed, AverageNightHours, TeamMaxHours and the budget mark a day or the roster and are not in it. The section shows how to check their setup (getRosterPayload()) and their result in a browser test (the list under the bar above the roster).

Fixed

  • The shift inbox named today's date for a rule break of the whole roster (a strict budget, a team-wide rule) that approving a swap would add. It now says "Whole team".

1.1.0 Nov 6, 2026

Added

  • Instructions for AI coding assistants (Claude Code, Cursor, Codex) through Laravel Boost: a guideline that Boost adds to CLAUDE.md and AGENTS.md, and the warp-shift-development skill for building rosters and testing them. Select qalainau/filament-warp-shift in php artisan boost:install, or add it to "packages" in boost.json. See AI coding assistants (Laravel Boost).

  • php artisan warp:assign-tenant "App\Models\Team" 1 (with --dry-run, and custom for a tenantKey() key): for apps that add tenancy later, gives the codes, rosters, staff needed, open shifts, availability and clock-ins saved without a tenant to one tenant, so the tenant panel shows them. Cells, requests and swaps move with their roster. Every row without a tenant moves, in one transaction; if the tenant already has a code key or a roster period that would clash, nothing changes and the command fails.

  • README: Adding tenancy to an app that already has rosters and Testing with tenancy (opening a tenant in a test, and what another team's IDs do: they are treated as not found, not as an error).

  • MinLeaveDays::yearFrom(fn (Employee $staff, CarbonImmutable $periodStart) => ...): a leave year per person, for leave that has to be taken within a year of the day it was granted. Return the first day of the year this period falls in, or null to leave the person out. A year runs for one year from that day (29 February to 28 February). A year that starts during the period counts leave from that day; a year that ends during the period is checked on its last day for the full number of days, and leave after it does not count. Replaces year() when both are given. takenBefore() and the leave counted from the roster use each person's own start. Marks the row in the roster as before, and in RosterEvaluation. README: A leave year per person.

  • navigationGroup() takes a closure (fn () => __('Shifts & attendance')), called each time the navigation is built, so the group is translated in the signed-in user's language. A translated string passed while the panel is configured was fixed in the app's default language.

1.0.0 Nov 4, 2026

Added

  • First release: monthly shift rosters for Filament 5.
  • ShiftRoster page on a <canvas>: type codes or labels (IME too), code list, copy and paste with Excel, fill handle with repeating patterns, undo and redo, pinned cells, groups, phone layout, dark mode. Saved by itself, with per-cell conflict detection. codes() limits a roster to its own shift codes.
  • Staff needed per shift for every day, weekdays, holidays or a single date, shown as staffed/needed under each day. Staff needed per time of day ("3 people from 11:00 to 14:00"), for anyone working or one shift, counted at every slot of the window (slotMinutes()); auto-fill fills windows with the shift codes that cover them. Staff needed from your app: requirements(fn (CarbonImmutable $date, string $scope) => [...]) per shift, place or time of day, stronger than the numbers on the roster and not editable there.
  • Rules checked as you type and on the server with the same results: MaxConsecutiveDays, AfterShift, MinRestHours, MaxHours, MinHours, MaxCount, MinCount, MinDaysOff, RequiredSkill, and requests. Errors or warnings, values per person, limited to some staff.
  • Auto-fill that keeps pinned cells and day-off requests, carries the previous period's nights over, spreads nights and weekends, tops people up to their hours and reports what is short.
  • Requests from staff with a deadline; publishing with versions and notifications only for people whose shifts changed; closing a roster. Requests have an "I'm done with my requests" button in My shifts, the people who responded in Collect requests, More → Remind about requests, and automatic reminders before the deadline (remindBefore(), the warp-shift:remind command).
  • My shifts for staff, swaps and cover (a night moves with its rest day; nobody can take a shift that breaks their own rules), Requests & swaps for managers with the rule breaks an approval would add, an iCalendar feed. myShifts(fn ($staff, $tenant) => bool) shows My shifts per tenant and per person (navigation and access); $tenant is the Filament tenant, or what tenantKey() returns in a panel without tenancy.
  • Open shifts (openShifts()): More → Post open shifts lists every short shift from today on (per shift, place and time of day) and posts them, auto-fill's notification offers the same, and a Staff needed number posts one shift for one day (also when it is not short). Only staff who are free that day, not helping elsewhere and would break none of their error rules (availability and who works together included) see them in My shifts and tap "I can work it"; a night brings its rest days along. Managers choose in Requests & swaps (with the reason when someone can no longer take it); choosing puts the cell into the roster and publishes a new version with only that change, closes the open shift when enough people are chosen and notifies everyone. openShifts(firstCome: true) gives it to the first person. Stored in warp_shift_open_shifts and warp_shift_open_shift_claims with the tenant columns.
  • Get a new address for the calendar feed in My shifts: the old address stops working at once (new table warp_shift_calendar_feeds). The feed of a deleted person stops too.
  • Days off and leave in the calendar feed as all-day free events: per roster with calendarDaysOff(), or per person with "Show days off and leave too" in My shifts (off=1 / off=0 in the address).
  • Excel and CSV download and a printable A3 view. 10 languages.
  • Notes on a cell (right-click → Note…, Shift + F2): saved and undone with the cell, published, shown in My shifts and the calendar feed, moved by swaps and cover, listed in Excel, CSV and print, and returned by the API.
  • MaxOvertime rule for Japan's 36 agreement: overtime over 8 hours a day and 40 hours a week (week start of your choice), monthly and yearly limits, the special clause (720 hours a year, 6 months over 45 hours), the law's limits of under 100 hours a month and an 80-hour 2–6 month average (checked with or without the special clause), holiday work on the statutory day off counted apart through legalHoliday() (a weekday, or the last day of a week without a day off), earlier months (with their holiday work) from your attendance records through priorOvertime(), OT and holiday work totals per person; auto-fill keeps to it as an error.
  • Japanese public holidays (JapaneseHolidays::between()) from the Cabinet Office list, with the years after it worked out from the holiday law.
  • PHP API: PublishedShifts reads the latest published version (with approved swaps) for clock-in, attendance or payroll, with times resolved to dates (nights end the next day); RosterPlan makes, replaces, merges and publishes rosters from code (optionally without notifications and at a given time); WarpShift::get()->asTenant() runs code for one tenant outside a panel, and currentTenant() gives that tenant (or Filament's) to your staffQuery(). Shift codes have a meta column for your own data, returned with each published shift.
  • Times typed into a cell (10-15, 9:30-14, full-width too) for hourly shifts: kept with the cell, saved, undone, published, moved by swaps, and used for hours, rest, overtime, cost, My shifts, the calendar feed, the API and the exports. timeCode() for empty cells, breaks() for the break by length.
  • The day by hour: a timeline of one day with drag to move and resize shifts, drag across an empty row to add one, and a chart of the people working at each time against the staff needed.
  • Places on a shift (places()): sites, posts or counters read from your own model, so a security or cleaning roster needs a few shift codes instead of one per site and time. Right-click → Place… or Shift + F3 puts a place on the selected working shifts; the cell shows a stripe in the place's color and its short label. Saved, undone, copied (D@TA), pasted and filled with the cell, kept when the shift changes, removed on a day off. Staff needed per place (also per time of day), each with its own row; auto-fill fills them with that place, and swaps during auto-fill and help from another roster keep places with shifts. Published and announced like a shift change, shown in My shifts, the calendar feed's location, Excel, CSV, print and the import; moved by approved swaps and cover; PublishedShift::$place and $placeName; RosterPlan takes 'place'.
  • Split shifts: two times in one cell (10-14,17-21), still one shift code per day. Hours, overtime, payroll, the break (from both times together, the gap is not a break), staff needed by time of day, night premium and labour cost count both times without the gap; rest between shifts runs from the end of the second. The day by hour shows two bars that can be dragged one by one; My shifts and the export show both times, the calendar feed makes two events, the import reads them; PublishedShift::parts(), isSplit(), $secondStartsAt; RosterPlan takes 'times' => '10-14,17-21'.
  • Availability (availability()): the days and hours each person can work every week ("Tuesdays and Thursdays only", "until 15:00 on weekdays", "Mondays from 17:00", holidays), with changes from a date. Staff register it in My shifts (phone width) and managers change it with right-click → Availability… in the roster (warp_shift_availabilities), or the app passes it with availability(fn ($staff) => […]) and the plugin keeps nothing and shows no form. Checked by the Availability rule (added as an error when not listed; Availability::make()->warn() for a warning) in PHP and in the browser alike, against the cell's typed times or the code's times. The roster shades days someone cannot work and shows the hours before anything is typed, with the reason in the tooltip and the week in the name's tooltip. Auto-fill puts nobody outside it (and avoids it when it is a warning), help from another roster does not offer them, "Why this person?" names it.
  • Whole-team rules: AverageNightHours (Japan's average night hours of a ward, with the night band, the hours that count a person, and hours per code) and TeamMaxHours, marked on the Staff heading and listed as "Whole team"; a Night total per person.
  • Help from another roster (borrowing()): borrow someone for a short day, offered in the order spare, free, day off and only when it breaks none of their rules; their home cell is cleared, they show under "Help from other wards", the day is striped and locked in their own ward, and one person can be on one roster of a page per day.
  • Fairness over the year (fairnessYear()): earlier periods of all wards counted against each person's fair share, a Fairness table, and auto-fill that evens out the year.
  • Labour cost from hourlyWage(), allowances() and nightPremium(), per day under the roster and in total above it (currency()), and a budget per period (budget() and More → Budget) as a whole-team warning or error; auto-fill does not add fill shifts past it.
  • Three or four drafts to compare in auto-fill (balanced, requests first, fairness first, lowest labour cost) with their rule breaks, shortages, requests kept, spread and cost.
  • "Why this person?" on a shift: the reasons and why each colleague is not on it.
  • Import a roster from Excel or CSV, read in the browser, checked in a dialog (people and days found, names and codes not found, only empty cells or replace) and put in like typing.
  • Payroll summary per person (days, hours, night hours, weekend and holiday days, overtime, holiday work, counts per shift, allowances, cost) across wards, from the published version, as Excel, CSV or PayrollSummary in PHP.
  • Clock-ins next to the plan (actuals()): passed from your own attendance table (one person at a time, or everyone at once with batch: true), with several clock-ins a day, night shifts on the day they started, open clock-ins and the minutes your app counted (worked, overtime, holiday, night); or, without a table of your own, imported from a time clock's CSV or Excel file (More → Import clock-in times: staff number or name, date, clock-in, clock-out, break; checked in a dialog, undone right after) into warp_shift_actuals. The Actuals switch shows the plan and the clock-in in each cell, colours late, early, overtime, no clock-in, missing clock-out and work without a shift (actualsTolerance()), adds an Actual column to the totals and clock-in bars to the day by hour; today's late and missing people show above the roster. Compared the same way in PHP and the browser. PayrollSummary::actuals() and More → Payroll summary from clock-ins give hours, night hours, overtime and cost from the hours actually worked.
  • RosterEvaluation: the roster's rule breaks and the hours, overtime and holiday work per person from your code, for any range of days and across wards, with settled days from clock-ins and the rest from the published roster (or the draft) — a projection of this month's 36 agreement figures (overtime(), nearLimits()), plus each day's late and missing clock-ins (attendance).
  • Who works together: NotTogether (at most one newcomer per night, or two people who never share a shift) and Together (a preceptor on every newcomer's night), by key, skill or only(), per shift code and optionally per place; checked in PHP and in the browser alike, kept by auto-fill (errors never broken, warnings avoided), named in "Why this person?".
  • Rotations: rotations() and staffRotation() (a pattern per person, counted from a start day or carried on from the end of the previous period); More → Apply a rotation (or right-click the rows) fills the rows you pick, leaving pinned cells, day-off requests and days someone cannot work, as one undo step; auto-fill can put rotations in first.
  • Leave balance: leaveBalance() with the LeaveBalance rule; leave requests in My shifts name a leave code and are refused past the balance; auto-fill keeps to it. MinLeaveDays warns about people behind on the leave they should take over the year.
  • Filament tenancy: codes, rosters, staff needed and everything on a roster are kept per tenant; the staff are limited to the current tenant through a relationship on the staff model (staffTenantRelationship()); IDs from another tenant are treated as not found; plugin settings (canManage(), staffForUser(), managers(), tenantKey()) apply per panel, so a panel with tenancy and one without can live in the same app. The tenant is stored as tenant_type and tenant_id, so panels with different tenant models (Team and Company) never mix rows with the same ID; a code key is unique per tenant in the database too. A tenant panel shows nothing before its tenant is known.

Filament + AI coding tips, by email

How to fit Warp plugins into your own app and pair them with Claude Code or Cursor: prompts that work, mistakes AI makes, real examples. Once or twice a month. Unsubscribe anytime.

Ask us anything about Warp

No email address or sign-up needed.

We read every question and answer here on the site, usually within a day. Others see your question after we have checked it.

What's stopping you from using Warp's plugins?

One question. We read every answer, and it decides what we build next. It is not shown on the site.

What's stopping you from using Warp's plugins?