Dashboard: keyboard triage queue for the Detections tab

Abierto
  • ¿Algo no está bien?
#27 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Tranquilo
Stack tecnológico
react, typescript
Área
accessibility, frontend, testing

Línea de trabajo

Start in apps/dashboard/components/detections-panel.tsx and inspect the existing detection list, detail pane, disposition flow, and tests; then run npm run test to understand current behavior. Add keyboard navigation, shortcut handling, and focus transitions while preserving the written-reason requirement and suppressing shortcuts in note and assignee fields. Done means the new key-handling tests pass, keyboard triage works end to end, and npm run lint plus npx tsc --noEmit are clean; bulk selection can be split into a separate PR.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement help wanted

The triage loop shipped in v0.3.0 and the product now tells operators to drive the untriaged count to zero. The UI makes that a mouse job.

Scored accessibility 4/10 in the 2026-07-25 review, and it is the widest gap against Splunk ES and Elastic Security. Analysts work a queue with the keyboard.

Task

In apps/dashboard/components/detections-panel.tsx:

  • j / k or arrow keys to move through the detection list
  • Enter to open the detail pane
  • Shortcuts for the common dispositions (a acknowledge, r resolve, f false positive, x accepted risk)
  • ? shows the shortcut list
  • Focus moves into the detail pane when it opens, and back to the list when it closes

Keep the note requirement intact. false_positive and risk_accepted still need a written reason, so those shortcuts should focus the note field rather than submitting.

Also worth doing here

Bulk selection. Twenty burst detections from one noisy week currently have to be closed one at a time, with a note typed into each. Shift-click range selection plus one disposition applied to the selection would fix it. Split into a separate PR if it makes the change easier to review.

Acceptance criteria
  • Keyboard navigation works without a mouse, end to end
  • Focus is managed when the detail pane opens and closes
  • Shortcuts do not fire while typing in the note or assignee fields
  • npm run test green, plus tests for the new key handling
  • npm run lint and npx tsc --noEmit clean
Notes

Not labelled good first issue because it touches the flagship feature and needs real care around focus management. Comfortable with React and accessibility work is the bar.

Lenguaje dominante
Python
Estrellas
10
Forks
5
Merge medio
9 h 7 min
PR fusionados (30 d)
116

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de blitzcrieg1/agentmetry

Todos los issues de blitzcrieg1/agentmetry

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.