We changed from a kanban board to scrum board, and added story points to all issues. We've added story points to each issue (see image linked below), but the estimates are not showing up on the board NOR on the backlog view. What am I missing?
For anyone experiencing anything like this... This was the response fro Atlassian, and it solved the problem.
Just found the root cause of the problem.
The Story Point custom field was without a search template.
This configuration you can see be accessing:
The option next to search template was set to None. I changed it to Number searcher and it fixed the problem.
Ah, great, thank you for chasing this up, and thank you ten times more for posting the cause!
I should have had the imagination to remember that a field with no searcher won't report correctly. I think I had forgotten because it is very very rare that an admin will remove a searcher from a field, especially an important one like story points.
In my case, I had the search template set to Number Searcher, but my Context was still set to 'Story' issues only. I expanded Story Points applicable issue types to 'Any issue type' and that seems to have gotten my story points propagating to the places I need (Backlog, sprint summaries, and Burndown Charts.
@Nic Brough [Adaptavist], We do have data for the field. We've entered story points. The screenshot you see from the first post has story points entered in.
So that grey dot on the list on the left is not mapped to 'story points, which I believe is the issue, but I'm not clear how to map that to that field.
I'm sure I'm missing something simple, but can't figure out how to get those story points to show up, and how to get total velocity to show up at the top.
It should be in the second picture you posted - the estimation field for the board (not the time tracking bit, just estimation). It would not be the first time I've run into Jira systems with more than one "story points" field, and the wrong one is selected!
Mmm. Can you have a look at three more things? All long-shots, but need to be checked.
@Nic Brough [Adaptavist], couple screenshots here:
Here is the scrum Board. You can see no estimates here either:
here is a single issue status. You can see the story points in the right column. This is in the "TO DO" column now.:
Here is the same issue with the 'status' column expanded so you can see the other status options:
So after running through everything previously posted here, I found that if you go to your project settings > Fields > In the top right click the "(gear) Actions" dropdown and select Edit Fields > scroll down to Story Points and click "Required" on the right for Story Points > Go back to your Projects backlog and try and create a new issue, it will bring up the full edit for an issue and yell at you for not having a story point value. Go ahead and enter a value and then create the issue. You will now note that it shows the story point value both on the issue in the backlog and in the info panel on the right for the issue (click on the issue to see this). Now you can go back and change Story points from Required to Optional and all future issues will have story points as an editable field on the right-hand info panel.
Anyone else experiencing this problem who doesn't have sufficient access rights to edit their fields might want to try this.
My board was configured with Estimation linked to Story Points. Editing the estimation in the preview screen (the little one on the left of the screen when you click on an issue) would populate the grey bubble on the story but not the Story Points field in the issue. Adding the story points to the field in the issue only did not populate either the grey bubble or the estimated value in the issue preview which was still showing as "unestimated".
I fixed this by changing the field in the board configuration, scrolling down the list of fields until I found the field Story points (note the lack of the capital P) and selecting this. This may be peculiar to our organisation's set-up but you have to select the right one or you won't get them to connect.
I've experienced similar issues when creating dashboards where there are multiple fields for status, start date, end date etc.
Hi everyone! My name’s Matt and I’m a product manager at Atlassian. I work in the navigation & findability space for all our Jira Cloud products. We’ve been working on trying to improve the exp...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event