psa-systems/mokosh-apps
Watch
9
0
Fork
You've already forked mokosh-apps
 0
Code Issues Pull requests 1 Projects Releases 14 Packages Wiki Activity Actions

feat(dispatch): Day / Week / Month view toggle on the Dispatch board (MAPPS-280) #317

Merged
YousifShkara merged 1 commit from feat/MAPPS-280-dispatch-week-month into main 2026-06-23 06:46:53 +02:00
Conversation 0 Commits 1 Files changed 1 +124 -24
YousifShkara commented 2026-06-23 06:41:38 +02:00
Owner
Copy link

The Dispatch board was day-only - any planning horizon longer than today required navigating back to the Calendar surface. Add a Day / Week / Month toggle to the toolbar (re-using the same CalendarView enum + ViewToggleButton component the Calendar already uses), expand the /dispatch?from=&to= data-fetch range to match the active view, and render the result through one of three grids:

  • Day stays the per-technician swimlane (the existing DispatchTimeline with on-call banner, availability, time-off).
  • Week renders the calendar's WeekGrid over the dispatch appointments - 7 columns of scheduled work, no per-technician swimlane this round (tracked as a follow-up under this ticket).
  • Month renders the calendar's MonthGrid - the existing calendar-grid summary, same appointments, scoped to the dispatch surface.

Title bar reflects the active range: Monday, March 5, 2026 in Day, Mar 3 - Mar 9, 2026 in Week, March 2026 in Month. Previous / Next step by one day / week / month respectively. The MAPPS-302 BigDispatch route picks all of this up because it embeds DispatchBoardPage directly - /big/dispatch?view=week style param wiring is the small follow-up that pairs the two tickets.

#MAPPS-280

The Dispatch board was day-only - any planning horizon longer than today required navigating back to the Calendar surface. Add a Day / Week / Month toggle to the toolbar (re-using the same `CalendarView` enum + `ViewToggleButton` component the Calendar already uses), expand the `/dispatch?from=&to=` data-fetch range to match the active view, and render the result through one of three grids: - Day stays the per-technician swimlane (the existing `DispatchTimeline` with on-call banner, availability, time-off). - Week renders the calendar's `WeekGrid` over the dispatch appointments - 7 columns of scheduled work, no per-technician swimlane this round (tracked as a follow-up under this ticket). - Month renders the calendar's `MonthGrid` - the existing calendar-grid summary, same appointments, scoped to the dispatch surface. Title bar reflects the active range: `Monday, March 5, 2026` in Day, `Mar 3 - Mar 9, 2026` in Week, `March 2026` in Month. Previous / Next step by one day / week / month respectively. The MAPPS-302 BigDispatch route picks all of this up because it embeds `DispatchBoardPage` directly - `/big/dispatch?view=week` style param wiring is the small follow-up that pairs the two tickets. #MAPPS-280
feat(dispatch): Day / Week / Month view toggle on the Dispatch board (MAPPS-280)
All checks were successful
Check / fmt + clippy + tests (pull_request) Successful in 1m8s
Details
Create release / Create release from merged PR (pull_request) Has been skipped
Details
751c81707e 
The Dispatch board was day-only - any planning horizon longer than today required navigating back to the Calendar surface. Add a Day / Week / Month toggle to the toolbar (re-using the same `CalendarView` enum + `ViewToggleButton` component the Calendar already uses), expand the `/dispatch?from=&to=` data-fetch range to match the active view, and render the result through one of three grids:

- Day stays the per-technician swimlane (the existing `DispatchTimeline` with on-call banner, availability, time-off).
- Week renders the calendar's `WeekGrid` over the dispatch appointments - 7 columns of scheduled work, no per-technician swimlane this round (tracked as a follow-up under this ticket).
- Month renders the calendar's `MonthGrid` - the existing calendar-grid summary, same appointments, scoped to the dispatch surface.

Title bar reflects the active range: `Monday, March 5, 2026` in Day, `Mar 3 - Mar 9, 2026` in Week, `March 2026` in Month. Previous / Next step by one day / week / month respectively. The MAPPS-302 BigDispatch route picks all of this up because it embeds `DispatchBoardPage` directly - `/big/dispatch?view=week` style param wiring is the small follow-up that pairs the two tickets.

#MAPPS-280
YousifShkara deleted branch feat/MAPPS-280-dispatch-week-month 2026-06-23 06:46:53 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
YousifShkara
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
psa-systems/mokosh-apps!317
No description provided.