faral/pokerface
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix 0-point estimate treated as unestimated causing poker loop
All checks were successful
Build & Push Container Image / build (push) Successful in 10s
Details

Browse source 
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>
This commit is contained in:
Jan Willem Mannaerts 2026-03-03 11:31:04 +01:00
parent 4f5c71e811
commit f17072116d
2 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

4
backend/src/services/jiraService.js
View file

@ -237,10 +237,10 @@ export async function getSprintIssues(jiraAccountId, sprintId, boardId) {
key: issue.key,
title: issue.fields?.summary || issue.key,
description: issue.fields?.description || null,
estimate: issue.fields?.[spField] || 0,
estimate: issue.fields?.[spField] ?? null,
status: issue.fields?.status?.name || 'Unknown',
reporter: issue.fields?.reporter?.displayName || null
})).filter((issue) => !issue.estimate);
})).filter((issue) => issue.estimate == null);
}
export async function updateIssueEstimate(jiraAccountId, issueIdOrKey, estimate, boardId) {