...
This could be possible due the use of one of the following reasons:
1) You are using a custom field or presence of duplicate fields for Story Point in your Jira instance and Project Settings. Therefore we instead of Jira’s default field. We strongly recommend using default Jira fields for time tracking and estimation that includes Story Points.
Another possibility is due to an inherent edge case in the Jira itself2) Wrong story point field. Earlier classic projects estimation were measured on “Story Points” “Story Points” field in Jira. Later they introduced another default field “Story “Story Point Estimate“ Estimate“ for next-gen and team managed projects that introduced a lot of confusion around Jira user community. This means if you’re using a classic project or company managed project template then you will have to configure and use default “Story Point” field, and if your project is created for next-Gen or team managed configurations then you will have to use default “Story Point Estimate” field. Yes, indeed it It is a Jira constraint currently and hence a pre-requisite for tracker.
If you are using a “Team-managed project” or “Next-gen projects”, the field should be “Story point estimate”
If you are using a “Company-managed project” or “Classic projects”, the field should be “Story Points”
3) Duplicate story point field or incorrect use of multiple story points fields available in Jira.
Multiple fields called “Story Points” or “Story Points Estimate”. If you are a Jira admin, you can go to https://yourinstance.atlassian.net/secure/admin/ViewCustomFields.jspa?page=1 and look for fields called “Story Points” or “Story point estimate”. If you find multiple fields, then you will have to remove the non standard one. It could be in the list of custom fields, or the Trash screen (if it is pending deletion). You can click on the “Info” icon to get some troubleshooting details, it should show you which field is currently being used by the tracker.
Indeed the multiple and wrong use of fields is confusing and the same has been recognized by Atlassian in their forums and support tickets.. Atlassian might be working on a fix long term but until then please make sure you have added the correct field for your project screens, removing the other one to avoid more confusion. Your Jira administrator can help you review your current configurations and help fix as necessary.
...