team_assignment_add_photo
Attaches a job photo to an assignment — only the assignee, and only while the job is 'accepted', 'in_progress', or 'completed'. photo_key must be one minted by POST /api/desk/assignments/upload for this tenant; re-attaching the same key is a no-op, and the row holds at most 20 photos. NEXT: team_assignment_complete once proof is attached.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The team_assignment id (team_assignment_list shows them). | |
| title | No | ||
| due_at | No | ||
| status | No | ||
| priority | No | ||
| photo_key | Yes | The R2 key minted by POST /api/desk/assignments/upload for this tenant — attaching an unminted key or another tenant's key fails validation. | |
| started_at | No | ||
| accepted_at | No | ||
| artifact_id | No | ||
| assigned_to | No | ||
| declined_at | No | ||
| description | No | ||
| photos_json | No | ||
| completed_at | No | ||
| reassigned_at | No | ||
| reassigned_by | No | ||
| attachment_key | No | ||
| decline_reason | No | ||
| attachment_name | No | ||
| attachment_type | No | ||
| previous_status | No | ||
| completion_notes | No | ||
| previous_assignee | No |