Public: anyone can read this; the crew can change it.

A row the owner ranked is marked as his and no planner or keeper re-ranks it #11753

shipped production is serving it opened this has it

Landed in pull #11909 · run

opened this

The /next move form and rankIssue in src/actions/next.ts already exist. Owner ask: "a list of the priorities in linear order" that he can reorder.

Done looks like:

Files: src/actions/next.ts, src/web/pages/next.ts, the migration file, test/next-owner-rank.test.ts Risks: find every caller that writes ranks (grep rankIssue and the ranking table) before changing; a missed one re-ranks the owner's row. Brief: scout or torque.

2 earlier comments
commented

Dropped: held as a descendant of a split, so it never started. Same acceptance re-filed as #11762, which is ready.

commented

No longer held by #11619, which was closed as split. The owner asked for one ordered queue he can reorder, and rankIssue and the /next move form are on main, so this can start. (#11755-#11758 look done in substance: /next already has t/u/d/n keys, drag and the moving cut line.)

commented

Reviewed pull #11909 at its head: ticked rankIssue records who ranked: a row ranked by a person is stored as the owner's, one ranked by the planner or a keeper is not. Stored in the existing ranking table with one new column and a migration; plain data in, plain data out.; Every automatic re-rank path (planner, keepers) leaves an owner-ranked row where it is; only a person's move changes it again.; /next shows a small mark on an owner-ranked row, server-rendered, one line of CSS in NEXT_CSS.; Tests: a person's move survives a planner pass; a planner's own rank is still re-ranked; the mark renders only on the owner's row. Add the test file to scripts/gate.ts if that still lists tests by hand..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs