I split the ticket id from the ticket key so that tickets could move between boards, and then I took moving tickets out of the product.

The split stayed. A key like ENG-42 gets pasted into WhatsApp messages, emails, GitHub PR titles and other tickets, and every one of those has to keep pointing at the right ticket for as long as the link exists, including after the ticket is gone.

I'm Panth, and I lead the software team at Oizom. This is from ticket-tracker , my open-source board, written to replace a tracker called TeamTrack. Its decisions page lists the choices that are expensive to reverse. This is D4.

The decision

Chosen A generated, immutable ticketId , a key field, and a keys index that keeps old keys as redirects

Rejected The key as the document id, which is what TeamTrack did with TICKET_ID

Why Keys change when a ticket moves.…