'Story Points' can't be updated - field is missing from the issue type

Owned by Björn Brynjar Jónsson
Last updated: Oct 08, 2022
3 min read

Notice, this problem only exists for Company Managed projects.

Similar errors can occur and the solution is different. More information on this here:

Learn more about the differences between Team- and Company- managed projects in Jira.

This problem users solve on their own with support-built-in

By default ‘Company managed’ projects are set up so that the ‘Story points’ field is associated with the following issue types:

  1. Epics

  2. Stories

  3. Bugs

When users try to save an estimate for other issues types the following error occurs:

"The field 'Story Points' isn't associated with the current issue type or project."

 

 

There is a quick solution to this problem

The solution is built-in

The video below shows how Smart Guess detects missing permissions and provides users with a short message and a direct link where users can update their settings to solve the problem. Here is how:

 

Step-by-step description:

Opening an issue where ‘Story Points’ field is not available

  1. Following warning indicator is shown next to the “Set Story Points” button

 

2. When clicked the following message is displayed “Story Points can’t be updated” as shown.

Note if the error text is different, then report an issue here.

 

Solving the problem

  1. By clicking the link “Update field configuration” the following screen is opned

2. By clicking the ‘1 context’ link in the table the following screen is opened

3. By clicking “Create, edit or delete context” the following screen is opened

4a. In this screen, as seen to the right, make sure ‘All issue types’ is selected.

Notice the error will occur for issue types not selected.

4b. In this screen, as seen to the right, make sure ‘Global context’ is selected.

Notice the error will occur for projects not selected.

 

5. Once these settings have been saved, you can open the issue in Smart Guess and now no warning appears.

 

 

6. You can now save the “Story point” value without any problems.