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; } } }

Velocity chart doesn't display Story Points value for past sprints

Dušan Stranatić

Hello,

In our Jira setup we had multiple Story Points custom fields. To reduce complexity, we removed all duplicated Story Points and migrated all values to a unique Story Points field. After the migration, redundant Story Points custom fields have been deleted from Jira.

Problem:
Velocity chart in a project that used one of the removed redundant Story Points fields doesn't show historic data (but only for the latest sprint since the team started using the unique Story Points field). Looking at tickets, they all contain this information in the unique field. Did anyone face with a similar situation? How can I "make" Velocity chart properly read value from the unique Story Points and display data for past sprints?

Many thanks in advance!

Best,

ds

P.S. I've already selected the unique Story Points field for estimates in the board setting page.

Accepted answers

Bill Sheboy

Hi @Dušan Stranatić -- Welcome to the Atlassian Community!

One lesson here: do not create additional story point fields and expect the built-in reporting to work.

The build-in reports, like the Velocity Chart, use the values in the built-in Story Points fields at moments in time using the issue history. And so even if the values are altered later the issue history cannot be altered. (Nor would you want it to be changed, as then it could not be relied upon.)

Going forward, your reports should be accurate if the correct fields are used when sprints start, progress, and end.

For historical data, it might be possible to extract the data an manually create the reports in tools external to Jira. After a few sprints have passed, that may not be relevant any longer.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Dušan Stranatić -- Welcome to the Atlassian Community!

One lesson here: do not create additional story point fields and expect the built-in reporting to work.

Going forward, your reports should be accurate if the correct fields are used when sprints start, progress, and end.

For historical data, it might be possible to extract the data an manually create the reports in tools external to Jira. After a few sprints have passed, that may not be relevant any longer.

Kind regards,
Bill

Dušan Stranatić

Thank you, @Bill Sheboy!

Much appreciate your answer.

Best,

Dušan

SUVARNA Dixit_uvovr9

how we can migrate story points from custom story points and unable to locate the inbuilt story point field

Bill Sheboy

Hi @SUVARNA Dixit

As this is an older thread, I recommend creating a new question. That will ensure more people see it to offer suggestions.

Until we see that...

There are two built-in story point fields for Jira Cloud:

for Company-managed projects, the field is named "Story points"
for Team-managed projects, the field is named "Story point estimate"

And, there are several ways to migrate the values from your custom field to the correct built-in one. For example:

create a JQL filter to find your issues, export them, and then import them to update the correct field
create a scheduled automation rule, using JQL to find the issues, and then copy the field over
use a marketplace app capable of copying fields between each other

Kind regards,
Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud