twotalesanimation
f30acef101
Deploy / deploy (push) Successful in 5m17s
A built package used to become DELIVERED on one click with nothing behind it, and nothing recorded what a client had asked for. - Marking delivered is now two recorded steps: Record upload (the link on the client's portal, contents confirmed) then Share link (who it was sent to). The second is refused until the first is on record. - Delivery requests log a client's ask by episode, pasted shot codes or a Shot Status selection. A line closes only when its shot goes out with evidence after the request was logged; a request can otherwise only be cancelled with a reason. - Delivered Outside Pipeline takes an upload link and recipient, required for shots on an open request. - The dashboard gains an Awaiting delivery section listing open requests and built packages the client does not have yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
9 lines
557 B
SQL
9 lines
557 B
SQL
-- "Delivered" used to be one click with nothing behind it. Record the upload
|
|
-- location and who was sent the link, so a package only becomes DELIVERED once
|
|
-- both have actually happened. Packages delivered before this keep NULLs here.
|
|
ALTER TABLE "delivery_packages" ADD COLUMN "uploadUrl" TEXT;
|
|
ALTER TABLE "delivery_packages" ADD COLUMN "uploadedAt" TIMESTAMP(3);
|
|
ALTER TABLE "delivery_packages" ADD COLUMN "uploadedById" TEXT;
|
|
ALTER TABLE "delivery_packages" ADD COLUMN "sharedWith" TEXT;
|
|
ALTER TABLE "delivery_packages" ADD COLUMN "sharedNote" TEXT;
|