feat(forms): breadcrumbs on Project / Contract / Asset create pages (MAPPS-294) #308

Merged
YousifShkara merged 1 commit from feat/MAPPS-294-breadcrumbs-consistency into main 2026-06-21 11:13:48 +02:00
Owner

New Ticket and Contact / Company create / detail surfaces already carried a breadcrumb trail back to their parent list, but the Project, Contract, and Asset create pages dead-ended on the form without a back-affordance, so the user had to use the browser back button (which after MAPPS-292 would trip the unsaved-changes guard on a dirty form for no good reason). Wire PageHeader { breadcrumbs: ... } on each missing surface so every create form opens with a back-to-list link in the same shape. Invoice create still needs the same treatment (its form is more complex) and is tracked as a follow-up under MAPPS-294.

#MAPPS-294

New Ticket and Contact / Company create / detail surfaces already carried a breadcrumb trail back to their parent list, but the Project, Contract, and Asset create pages dead-ended on the form without a back-affordance, so the user had to use the browser back button (which after MAPPS-292 would trip the unsaved-changes guard on a dirty form for no good reason). Wire `PageHeader { breadcrumbs: ... }` on each missing surface so every create form opens with a back-to-list link in the same shape. Invoice create still needs the same treatment (its form is more complex) and is tracked as a follow-up under MAPPS-294. #MAPPS-294
feat(forms): breadcrumbs on Project / Contract / Asset create pages (MAPPS-294)
All checks were successful
Check / clippy + fmt + tests (pull_request) Successful in 1m28s
Create release / Create release from merged PR (pull_request) Has been skipped
d32a77b12d
New Ticket and Contact / Company create / detail surfaces already carried a breadcrumb trail back to their parent list, but the Project, Contract, and Asset create pages dead-ended on the form without a back-affordance, so the user had to use the browser back button (which after MAPPS-292 would trip the unsaved-changes guard on a dirty form for no good reason). Wire `PageHeader { breadcrumbs: ... }` on each missing surface so every create form opens with a back-to-list link in the same shape. Invoice create still needs the same treatment (its form is more complex) and is tracked as a follow-up under MAPPS-294.

#MAPPS-294
YousifShkara deleted branch feat/MAPPS-294-breadcrumbs-consistency 2026-06-21 11:13:48 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
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!308
No description provided.