pokerface/frontend
Jan Willem Mannaerts f17072116d
All checks were successful
Build & Push Container Image / build (push) Successful in 10s
Fix 0-point estimate treated as unestimated causing poker loop
Root cause: estimate field used || 0 which collapsed both null
(never estimated) and 0 (estimated as zero) into the same value.
The filter !estimate then matched both, so saving 0 points left
the issue in the unestimated list and advanceToNext re-pokered it.

Fix: use ?? null so 0 is a distinct valid estimate, and filter on
== null to only match truly unestimated issues.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-03 11:31:04 +01:00
..
public Initial commit: Pokerface sprint planning poker for Jira 2026-02-26 21:38:37 +01:00
src Fix 0-point estimate treated as unestimated causing poker loop 2026-03-03 11:31:04 +01:00
.env.example Initial commit: Pokerface sprint planning poker for Jira 2026-02-26 21:38:37 +01:00
index.html Initial commit: Pokerface sprint planning poker for Jira 2026-02-26 21:38:37 +01:00
package-lock.json Initial commit: Pokerface sprint planning poker for Jira 2026-02-26 21:38:37 +01:00
package.json Initial commit: Pokerface sprint planning poker for Jira 2026-02-26 21:38:37 +01:00
vite.config.js Initial commit: Pokerface sprint planning poker for Jira 2026-02-26 21:38:37 +01:00