#48 Open issues first in table

closedarea:renderm6-polishopened
details
updated
id
78c8e17f-f558-4544-b88d-d29ba5a76e65

Context: Owner QA — open issues should top the issues table. Tasks:

  1. Issues index sort: open first (reverse-chron within), then closed (reverse-chron within). Same for pulls (open incl drafts first, then closed/merged). Display numbers unchanged (still creation rank).
  2. Add small group labels? NO — keep one table, open block then closed block (a hairline divider row is fine, keep tiny).
  3. Tests: fixture mixed states asserts row order + numbers stable. Swarm: pair with #49 (same sort code). Branch m6/sort.

Comments (1)

all issues