Scanning boards using JET apps returns “Critical error occurred while getting estimated stories negative count” error

Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Scanning boards in Jira using JET apps returns a “Critical error occurred while getting estimated stories negative count” error.

Environment

Jira Align

Cause

The root cause is from a custom field chosen in the "Map your Configuration" page that is not linked to the Screen associated with the scanned project, or it may be due to an unsupported custom field type.

Step to reproduce

  • Select “Project Settings”

  • Expand “Apps“ and select “Jet“

(Auto-migrated image: description temporarily unavailable)
  • Click “Let's get started“

  • Select the board you want to scan and click 'Next'

  • Select the “fede1cumstomfield(cf[10212])“ that is the 'text' type for the “story Points Custom Field“

(Auto-migrated image: description temporarily unavailable)
  • Click “Analyze your board” and you will see this

(Auto-migrated image: description temporarily unavailable)
  • An error occurred when the "Map your Configuration" field had a wrong custom field for the "story point custom filed" that is not associated with the Screen associated with the project or the custom field type is text instead of a numerical

Solution

Select the appropriate custom field in the "Map your Configuration" section for the "story point custom field" linked to the project screen.

Updated on April 14, 2025

Still need help?

The Atlassian Community is here for you.