Force story points to appear on all task types across several projects and boards - company managed

[Lloyd Bullard]

What it says in the title. 

I am using a company managed set of projects, and we are running a single board for sprint planning. 

I am unable to get the story points field to appear in tickets and in the backlog/active sprint board. 

there appear to be five or so ways of making story points appear, however I would like a simple straightforward answer as a lot of the articles I am reading relate to older versions of JIRA. 

[Trudy Claspill]

Hello @Lloyd Bullard 

Welcome to the community.

In your Board Settings, what options have you selected for Estimation?

Can you provide a screen image of what you are seeing in the Backlog an on the board where you think Story Points should be showing?

[Lloyd Bullard]

please see above for the estimation settings in the board, as well as an open ticket from the current sprint with no story points showing. 

I have gone through and added story points to the default issue screen under the context fields, but I am still only seeing them for stories and not for tasks or sub tasks. 

this was working prior to moving from a team managed to company managed set of projects/boards. noting we have one board with a view into four different projects. the projects have a unified workflow and ticket structure, allowing me to manage sprint planning when the team might be doing bits of work across multiple backlogs from the separate projects. 

[Trudy Claspill]

Hello @Lloyd Bullard 

Are you aware that Team Managed projects and Company Managed projects use two different fields for Story Points? In Team Managed projects the field is called Story Points Estimate. In Company Managed projects you need to use a field called just Story Points.

Have you worked with Company Managed projects before? Are you knowledgeable about the differences in how the configurations of the projects are managed, with Company Managed projects using Schemes for field configurations, screens, workflows, and issue types?

A field needs to be available in a Field Configuration that is part of the Field Configuration Scheme that is associated to the project. In the Field Configuration Scheme, Field Configurations are associated with Issue Types. Check the Field Configuration Scheme associated to the project to see which Field Configurations it uses. Make sure the Story Points field is in those Field Configurations.

Next you need to make sure that the Story Points field is included in the Screens that are used in the project.

Screens are created for the different issue operations; Create, Edit, View. The association of Screens to Operations is done in Screen Schemes. Then in an Issue Type Screen Scheme, the Screen Schemes are associated with Issue Types. Check the Issue Type Screen Scheme associated with the project. Check each of the Screen Schemes in that Issue Type Screen Scheme. Check each of the Screens in the Screen Schemes. Make sure that the Story Points field is on each screen.

After that you could then click on the Configure option you see when viewing an issue. Make sure that the Story Points field has been added. You would add it to the Context Fields section. You can decide if you want it in the section that hides empty fields or shows the fields even when they are empty. You want to click Configure while viewing a sample issue for each type of issue you use in your project.

Finally, at that point, the Story Points field should be available. The value should display on cards on the board and in the backlog screen in a small grey circular lozenge.

[Lloyd Bullard]

Hi Trudy, 

thanks for your thorough comment last year, I have only now had the time to sit down and give this the proper attention it needed. 

regarding your questions on my previous JIRA experience - I have been using JIRA on and off for over 10 years now. I worked extensively with the old on prem version of JIRA as an admin several years ago. the last two years I have been using JIRA next gen (what is now called team managed) and Azure devops. this is my first return to the "company managed" style JIRA project. part of my issue when I hit a wall like the one I am encountering is finding documentation relevant to the specific version of JIRA I am using. the company managed documentation I have found does not outline everything you have said above. 

Thanks for the thorough walk through, I have spend the last two hours checking everything you listed. "story points" were already added to the field configuration scheme for all of the projects I am using - I copied the default scheme and modified it slightly by attempting to add story points to all issues when we shifted to JIRA last year.

checking in all of the above places you listed story points were missing from bugs, however they were on everything else. I am still not seeing them on all ticket types ( see screenshot). do you have any further ideas on what I can try, or documentation/screenshots/video walkthroughs I can follow to make sure I have not missed something? I have already spent too much time on what should be a very minor issue. 

Kind regards, 

Lloyd

[Trudy Claspill]

In the latest screen image you are showing that the field is not visible on issue cards shown in the Board. Is the field shown when you look at the Issue Details? Does the field have a value?

Can you show us screen images of the issue details for the two issues for which you showed us cards?

If the field is not visible when you are viewing the issue details, you can click on the ... (ellipses) button in the upper right corner and select the "Find your field" option to find out why a field is not displaying in the the issue details screen.

You noted that story points are not visible on subtask type issues. Generally story points are not intended to be used to estimate subtasks. Story points are used to estimate the items that can be assigned to sprints. Subtasks can't be assigned to sprints separately from their parent issues and so generally are not estimated with separate story point values. Because of this, Jira does not show the Story Points field on cards for subtask type issues. If you want to show it on those types of cards you would need to added it to the Card Layout, and then it would show up twice on the non-subtask issue type cards.

For standard issue types (story, task, bug, etc.) the field should show on the card if it:

- is in the field configuration used by that type of issue in that project

- is included in the Create, View, and Edit screens for that type of issue in that project

- has a value assigned to it in the specific issue

- The Board Settings for Estimation have the Estimation Statistic set to Story Points

- the Board Settings for Estimation have the Time Tracking option set to None. If it is set to Remaining Estimate and Time Spent, then on the cards the Remaining Estimate will be shown instead of Story Points