Summary

Story point field not available in the Plan

Environment

Cloud

Diagnosis

• The field is not restricted with context, however, the rest are also not using the context. So this should not be the problem.

  select * from fieldconfigscheme where fieldid like '%<customfieldID>' 

• Adding the field to the plan using API didn't work. No error on the HTTP request but the field still missing.
• The field is not listed when even on selecting 'unsupported'.
• https://<sitename>.atlassian.net/rest/jpo/1.0/customfield/getAll is not returning the field.

• Problematic custom field

  id	cfkey	customfieldtypekey	customfieldsearcherkey	cfname	description	defaultvalue
  10023		com.atlassian.jira.plugin.system.customfieldtypes:float	com.atlassian.jira.plugin.system.customfieldtypes:exactnumber	Estimated Effort (Days)	How long do you estimate this piece of work SHOULD take, in DAYS (e.g. 1.5).
  10116		com.atlassian.jira.plugin.system.customfieldtypes:float	com.atlassian.jira.plugin.system.customfieldtypes:exactnumber	Estimated Effort Remaining (Days)	Estimated number of days remaining to complete the feature.

Cause

The field Estimated Effort (Days) is actually the Story Points field. The field was renamed in the past which caused the misunderstanding.
The Story Points field is part of Jira Software and it has some special settings assigned on the background.
On the plan, we can select the type of estimation you'll be using. If we choose Story Points, the field will be available.

Solution

The settings on this site were not incorrect, but the different name on the field causes some confusion.

To fix the issue, update the field back to the name "Story Points" name and create a new one for Estimated Effort (Days).