Possible Causes and Solutions
Excessive Custom Fields
If your Jira instance has too many custom fields, it can cause failures when loading the backlog or the board, as documented by Atlassian. Jira attempts to load all fields and may fail if the count is too high.
Solution: Reduce the number of custom fields. If this is not possible, contact Atlassian Support.
Estimation / Board Configuration Error
The error may be related to the board's estimation settings (e.g., Story Points or Time), especially if the board covers multiple projects or issue types.
Solution: Check the board settings under "Board Settings" > "Columns" and "Estimation". Ensure all statuses are correctly mapped and the estimation field is properly configured.
Permissions or Blocked Statuses
If backlog item statuses are not correctly mapped to board columns, or if there are restrictive permissions, it may prevent viewing the backlog or starting a sprint.
Solution: Confirm that the "Backlog" status is correctly mapped and verify that you have the "Start Sprint" permission.
Temporary Issues or Atlassian Infrastructure
Sometimes, the error is caused by temporary instabilities in the Atlassian infrastructure.
Solution: Try clearing your browser cache, using a different browser, or waiting a few minutes. If the issue persists, report the error to Atlassian Support and provide the specific error Hash.
Recommended Steps
Review the board configuration and the total number of custom fields.
Verify that all statuses are correctly mapped to the board columns.
Confirm you have the necessary permissions to manage and start sprints.
If the problem persists, contact Atlassian Support and provide the Error Hash: 1S3Z24I.
Status Update Template (Investigation)
Based on your saved preferences, here is the formatted update for this case:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.