I have used Jira for many many years but always at organizations that had Jira admins on staff setting up and managing our environments. I am now deploying my own Jira environment for a new company and running into issues understanding the multiple story point fields and why they dont seem to work properly as well as why story points do not burn down properly when items are completed. I have seen conflicting information online about story points vs. story point estimates fields and which one we should be using and information on setting the resolution to properly close things but I cannot seem to find that field in our system to add it to a form. Any help or guidance would be helpful. Thanks!
Hi @Cris Coffey -- Welcome to the Atlassian Community!
Regarding story point fields...
When team-managed projects (TMP) were added, Atlassian made a design choice to add a new field: "Story point estimate". The "Story points" field is the global one still used for company-managed projects (CMP).
In the UX for TMPs, the field is inconsistently called "Story point estimate" and "Story points", but both refer to the new field.
Kind regards,Bill
Where's my rolling eyes emoji gone
We are using Company Managed Projects so this is helpful and explains why all the data we imported into the Story Point Estimate field was not showing up in our sprints. We copied all the values into the "Story Points" field and the points started showing up. Now we are just having the issue where the Burndown report shows everything totaled on the red open issues line with nothing closing as we close out items. Most of these issues were added after the sprint started and then dumped into the sprint. Is that why this is not working? Is it not possible to add scope to the sprint after it starts and reflect it properly in the burn down chart?
I recall the guideline on the burn charts is based on the scope when the sprint starts, and so if all of the story points we set after sprint-start, the chart will be wrong.
Regarding burning down values, is your final workflow status mapped to the right-most column of the board? That is how Jira Scrum board detect completion for burndown.
It looks like you're new here. Sign in or register to get started.
