feat(board): paste client feedback from WhatsApp
Deploy / deploy (push) Successful in 3m34s

"Paste feedback" on each board card takes a client's message as it arrived
and splits it into rounds ("FEEDBACK 113 DUE Oct 7 12:00 PM") and per-shot
notes, tolerating WhatsApp copy prefixes, bold markers, wrapped lines,
several codes per note and codes without the show prefix.

A review step shows each note's shot, the version the client was sent,
the player frame and a "move task to Changes" tick (on by default).
Saving creates a FeedbackRound, a player comment per note tagged
source=WHATSAPP (shown as "Client feedback") and a board line under the
round's due time; ticking the line off resolves the comment.

Quoted frames are read as comp frames: shot frameStart or the house 1001,
plus the slate (recorded, else 1 for pipeline previews). Version.duration
is never stored on live, so the length-based slate inference can't be used.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
twotalesanimation
2026-10-07 17:31:34 +02:00
parent 34af26dfbf
commit 842a8fe036
12 changed files with 1073 additions and 8 deletions
@@ -0,0 +1,22 @@
-- Client feedback pasted from WhatsApp: rounds group the notes on the board,
-- and each note is saved as a player comment tagged with its source.
ALTER TABLE "comments" ADD COLUMN "source" TEXT;
CREATE TABLE "feedback_rounds" (
"id" TEXT NOT NULL,
"projectId" TEXT NOT NULL,
"title" TEXT NOT NULL,
"dueAt" TIMESTAMP(3),
"createdById" TEXT NOT NULL,
"createdAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP,
CONSTRAINT "feedback_rounds_pkey" PRIMARY KEY ("id")
);
ALTER TABLE "board_items" ADD COLUMN "roundId" TEXT;
ALTER TABLE "board_items" ADD COLUMN "commentId" TEXT;
CREATE INDEX "feedback_rounds_projectId_idx" ON "feedback_rounds"("projectId");
ALTER TABLE "feedback_rounds" ADD CONSTRAINT "feedback_rounds_projectId_fkey" FOREIGN KEY ("projectId") REFERENCES "projects"("id") ON DELETE CASCADE ON UPDATE CASCADE;
ALTER TABLE "board_items" ADD CONSTRAINT "board_items_roundId_fkey" FOREIGN KEY ("roundId") REFERENCES "feedback_rounds"("id") ON DELETE SET NULL ON UPDATE CASCADE;
+28
View File
@@ -390,6 +390,7 @@ model Project {
boardStatusAt DateTime?
boardItems BoardItem[]
milestones ProjectMilestone[]
feedbackRounds FeedbackRound[]
@@map("projects")
}
@@ -612,6 +613,10 @@ model Comment {
timestamp Float
text String @db.Text
isResolved Boolean @default(false)
/// Where the note came from when it was not typed in the player. "WHATSAPP"
/// = client feedback pasted from a message; `authorId` is then whoever
/// logged it, not who said it, and the player labels it client feedback.
source String?
createdAt DateTime @default(now())
updatedAt DateTime @updatedAt
@@ -1288,6 +1293,12 @@ model BoardItem {
assignee User? @relation("BoardItemAssignee", fields: [assigneeId], references: [id], onDelete: SetNull)
/// What the line is blocked on ("client GFX ADH_GFX_013_010"); null = not blocked
waitingOn String?
/// Set when the line came from pasted client feedback: the round it belongs
/// to, and the player comment it was saved as. Ticking the line off
/// resolves that comment.
roundId String?
round FeedbackRound? @relation(fields: [roundId], references: [id], onDelete: SetNull)
commentId String?
sortOrder Int @default(0)
doneAt DateTime?
doneById String?
@@ -1300,6 +1311,23 @@ model BoardItem {
@@map("board_items")
}
/// One batch of client feedback as it arrived ("FEEDBACK 113 DUE Oct 7 12:00
/// PM"). Its notes are saved as player comments and as board lines; the round
/// is what groups them on the board under one due time.
model FeedbackRound {
id String @id @default(cuid())
projectId String
project Project @relation(fields: [projectId], references: [id], onDelete: Cascade)
title String
dueAt DateTime?
createdById String
createdAt DateTime @default(now())
items BoardItem[]
@@index([projectId])
@@map("feedback_rounds")
}
/// A dated project milestone — batch deliveries, picture locks, shoot start,
/// colour & mix review. Episode due dates stay in EpisodeDueDate because the
/// shot-status board keys off them; these are the dates around the work.