Linear List Integration Block for React

Tab enters the list once, at the current row (its Accept, Decline and, when needed, Retry buttons are the only ones in the tab order). With focus on any of them, J or the Down arrow moves to the next row and K or the Up arrow to the previous one, A accepts and D declines (in Triage), and focus follows to the next row. The handlers sit on those buttons, not on the document, so typing anywhere else on the page never triggers them. These are this block's keys, not Linear's own shortcuts.

Edit START at the top of the file: each issue has an id, its code (team key and number, like WEB-214), a title, a priority (urgent, high, medium or low), an estimate, a starting place and a sync of ok or failed. The tab counts, the rows and the unseen copy that holds the height all derive from that list. In a real product, replace the local decide, back and retry functions with your calls.

No. A decision moves the row between tabs on this page and the status line says what would happen in Linear: an accepted issue moves to its team's default status, a declined one gets a Canceled status. The line is in the page from the first paint and always ends with "Nothing was sent". Retry shows the row as syncing for about 900 milliseconds and then fine. Back to Triage returns a decided row.

The tabs are real tabs with panels. Each button names its issue ("Accept WEB-214", "Retry the estimate of WEB-219"). The priority mark is decorative; its word is in the text. The status line is polite and announces each decision, and when the last row of a list is decided focus returns to the selected tab. Tab counts are in the tab names.

On a phone the buttons wrap under each title and the key hints are hidden (the buttons stay). Issue keys keep their reading order in a right-to-left layout while the rows flip. The header fades up once on load and nothing else is animated; with reduced motion it simply appears.