Skip to content

Schedule status accepted in API request data but never persisted #337

@jbrooksuk

Description

@jbrooksuk

Priority: P2 (High - Fix Soon)

Problem

Both CreateScheduleRequestData (src/Data/Requests/Schedule/CreateScheduleRequestData.php:24) and UpdateScheduleRequestData (:17) accept a ScheduleStatusEnum $status property.

However, the status column was dropped from the schedules table in migration 2024_10_13_214300. The Schedule model computes status from scheduled_at/completed_at via an Attribute accessor. Any status value sent via the API is silently ignored.

Suggested Fix

Remove the $status property from both request data classes, or validate and map it to completed_at if the intent is to let API consumers set a schedule to "complete".

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions