noCV
CCAL-104 · Operate shifts

Move staffing shifts through a keyboard form

Practice briefStoryIntermediate

Dragging is the only way to move a shift. Add date/time controls with equivalent validation.

Focused work estimate
2h 30m + prerequisites
Priority in the scenario
High
Engineering practice
Keyboard · Forms

Estimated field mix

  • Accessibility60%
  • Frontend40%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

Review it, then add it to your workspace.

The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.

Use in my work boardView project and downloads

Project context

Fictional studio Loom assigns editorial shifts. Build synthetic shifts and a local scheduling adapter; no real staff records are used.

Setup prerequisites

  • Create synthetic shifts including overlaps and daylight-saving boundaries.
  • Implement a local schedule revision adapter.

Preceding work

Complete these dependencies, or supply their agreed outputs before taking this ticket.

Acceptance criteria

  • Every draggable shift has Move action
  • Form and drag share validation
  • Cancel preserves the shift

Implementation constraints

  • The form must not require pointer gestures.

Verification to include

  • Move using keyboard
  • Submit overlapping invalid shift

Deliverables

  • Move form and equivalence cases

Rollout and recovery

Disable dragging if it diverges from the form contract.

Value of the work

For the engineer: Practice focus models and accessible alternatives for spatial interfaces.

For the team: Inspect whether scheduling remains usable across input methods and failure states.

Evidence boundaries

Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.

Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.