Moving tickets between st8n and Deleg8

Only for people who used st8n’s own Tickets before: Deleg8 does not need st8n, and nothing here is required.

Into Deleg8

On the server, with Deleg8 stopped and from its folder, run DELEG8_DATA_DIR=server/data/db node server/src/import.ts --db ~/.station/tickets.db --person <account id> (your account id is person.id in GET /api/v1/me; DELEG8_DATA_DIR is wherever your data lives, or DATABASE_URL for Postgres). st8n’s Inbox goes into your Inbox. Every other list, ticket and timeline entry comes across, along with who did each thing, the batches, and who owned each list. Running it again adds nothing twice. The file is only read, never changed.

Back to st8n

DELEG8_DATA_DIR=server/data/db node server/src/export.ts --person <id> --out <new file> --site <name> (Deleg8 stopped, as above), writes a new tickets.db. What came from that st8n gets its old ids back. Work made in Deleg8 gets the next free ids, and its done when goes into the details. With st8n stopped, put the file at ~/.station/tickets.db.

What is proven

A test builds a realistic tickets.db with st8n’s own code. It has five lists (including one a member made and one archived), sixteen tickets in every status, two held mid-work, a claim that lapsed until it was blocked, batches, edits and moves. The test sends a copy of it into Deleg8 and back out, then compares the result with the original, row by row. They are the same, except for:

• A ticket a session was holding comes back open, with a timeline line naming the session and computer that held it.
• Work tokens don’t move. They are secrets, so make new ones where you need them.
• The Inbox keeps Deleg8’s own created and updated times.

st8n’s own store then opens the file, and numbering carries on where it left off.