Story point estimate is not available as an estimation method

Question

The JIRA default "Story point estimate" custom field (which is locked), is not available as an estimation method on our project boards.

The field is not hidden and is visible on Stories, Bugs and other subtasks, so the context and association is not the problem.

Does anyone have an idea why this is?

Trudy P Claspill · Answer

Hello @Dez-Luan

Are you working with a Team Managed project or a Company Managed project?

From the board image you provided I can tell that you are not looking at the board created natively for a Team Managed project. You may be looking at the board created natively for a Company Managed project, or you may be looking at a board created from a filter that can reference any type of project.

The Story Point Estimate field is intended to be used only with Team Managed projects. Story Point Estimate in Team Managed projects is the equivalent of Story Points in Company Managed projects.

It is a special custom field type - Story point estimate value - so it will not be available in the Estimation option for your board. As @Matt Parks mentioned, only Number custom fields are available there.

If you are working with a Company Managed project, is there a reason you don't want to use the native "Story Points" field for your Company Managed project?

If you want a "story point estimate" field separate from the native "story points" field for your Company Managed projects, you will need to create a new Number type custom field for that. Note that Jira does allow you to create custom fields with the same name as existing fields, but that is not a good idea because it can lead to confusion. So, if you decide you must have that field, give it a name that is different in some way from the native "Story point estimate" field.

Dez-Luan · Answer

Yes, it's JIRA's built in field

Bill Sheboy · Answer

Hi @Dez-Luan

Unfortunately (in my opinion), there are currently two different story point fields in Jira Cloud:

* Story points: used by company-managed projects
* Story point estimate: used by team-managed projects

The UI is inconsistent in some places, either only referring to "Story points" or explicitly showing the correct name for the project type.  This field difference is mostly relevant for automation rules and when moving issues between projects of different types.

What problem are you trying to solve by specifically selecting that field?

Kind regards,
Bill