nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Story Points Display As a Dash in Boards

Fred Bidel

Despite having estimated our User Stories, and even though Story Points display in the Detail View, the Board view shows Story Points as a dash or hyphen.

Below is an example of what it looks like:

https://www.screencast.com/t/bdce65POuDc4

We are using the web version of JIRA. Everything else looks and works fine.

Any help would be greatly appreciated since this is forcing us to click on each User Story just to see their Story Points.

Thanks,

Fred.

Accepted answers

Fred Bidel

I received the following information from Atlassian's support team, and it solved the matter.

"After some time investigating this issue, I found out that the root cause is that the field was edited and a configuration was changed.

In https://dcimarketing.atlassian.net/secure/admin/EditCustomField!default.jspa?id=10004, the Search Template settings were changed from Number searcher to None."

This came from Gabriel Müller, Atlassian Cloud Support.

Thanks again Gabriel! :-)

All comments

Tinker Fadoua

Hi Fred,

Did you check the board configuration?

Check if you have the following:

Screen Shot 2018-01-17 at 1.53.47 PM.png

Fred Bidel

I checked both, and they are set up exactly as you suggested. I added a screenshot of how the Story Point fields look like in our Backlog.

https://www.screencast.com/t/bdce65POuDc4

Tinker Fadoua

ok let me check what can be the problem. I will get back to you

Tinker Fadoua

I know it may sound silly, however did you try a different "Estimation Statistic" and then go back to "Story Points"?

I tried myself everything I can on my board but didn't get any dashes.

Fred Bidel

Thanks for the suggestion. I tried it but it did not work. I have been using JIRA for years; this is the first time I have seen anything like this myself.

Tinker Fadoua

Let me go back here? How long have you been experiencing this behavior? Did you have it before or did it just start?

If it just started: what change you made recently? It could be behind this issue.

Fred Bidel

That feature has been behaving like that since Day 1. We have been trying to find the cause of it, but we have been unsuccessful so far.

Tinker Fadoua

Hi Fred,

I didn't forget about you, then something must have gone wrong during install.

The following is what I found on one of Atlassian docs:

Note that, by default, the Story Points field is only available to issues of type 'Story' or 'Epic' — you can change this as described in jira agile - jira configuration

Database tables

When you install the JIRA Agile add-on into your JIRA instance, the following additional tables will be created in your JIRA database to store rank, configuration and sprint information:

'AO_60DB71_COLUMN'
'AO_60DB71_COLUMNSTATUS'
'AO_60DB71_ESTIMATESTATISTIC' (added around 5.9.5)
'AO_60DB71_ISSUERANKING'
'AO_60DB71_ISSUERANKINGLOG'
'AO_60DB71_QUICKFILTER'
'AO_60DB71_RANK_ISSUE_LINK'
'AO_60DB71_RAPIDVIEW'
'AO_60DB71_SPRINT'
'AO_60DB71_STATSFIELD'
'AO_60DB71_SUBQUERY'
'AO_60DB71_SWIMLANE'
'AO_60DB71_TRACKINGSTATISTIC'

Fred Bidel

Thank you for this information. There is one issue though: we are using the online version of JIRA and not a local install. Does the above information apply to the online version too?

Tinker Fadoua

My best suggestion since you are using the Cloud version is to open a ticket with Atlassian and report this issue. There isn't much you can do as a JIRA Admin when on Cloud Version

https://support.atlassian.com/contact/#/

Best of luck!

Tinker Fadoua

Story Points for Cloud Users:

https://confluence.atlassian.com/jirasoftwarecloud/configuring-estimation-and-tracking-764478030.html

Fred Bidel

I received the following information from Atlassian's support team, and it solved the matter.

"After some time investigating this issue, I found out that the root cause is that the field was edited and a configuration was changed.

In https://dcimarketing.atlassian.net/secure/admin/EditCustomField!default.jspa?id=10004, the Search Template settings were changed from Number searcher to None."

This came from Gabriel Müller, Atlassian Cloud Support.

Thanks again Gabriel! :-)

Abraham Vallez

I received an answer too.

I had a look on your instance and found that the Story Points field configuration was updated by one of your users. It is specifically for the Search Template which was changed to None; causing the Story Points shown as dash.

I have changed it back to the correct value and you should be able to see the Story Points again.

Tinker Fadoua

Thank you so much guys for taking time to inform us about the fix for the issue!