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 are not synchronized in Portfolio

unknown

Hi,

I am creating a plan in Portfolio and I have a problem. I chose Story Points as the planning unit and none of the stories or epics show any Story Points in my plan. However many stories have Story Points in JIRA. When i change to hours, I can see hours from the stories but nothing if I choose story points...

The Story Point field I chose is the same as the one used in the Agile Board.

Can you help me?

Thanks a lot

Accepted answers

Allard van Helbergen

Hi Nicolas,

How's it goin'? Sorry to hear that it's not working for you. We've seen this kind of behaviour for when projects have erroneous duplicate custom fields. This seems to happen through past failed upgrades or (de)installation of plugins.

Portfolio will always refer to the default story points field. If you could check in your admin settings if there is a duplicate custom field for story points and then set all your projects to use the default one.

If the above doesn't seem to be the case for you, I would ask you to file a support ticket so that we can take a closer look.
https://support.atlassian.com/servicedesk/customer/portal/28

Cheers,
Allard

All comments

Allard van Helbergen

Hi Nicolas,

If the above doesn't seem to be the case for you, I would ask you to file a support ticket so that we can take a closer look.
https://support.atlassian.com/servicedesk/customer/portal/28

Cheers,
Allard

unknown

Hi,

Thanks for the very quick answer!

I found the problem and it is hilarious (or sad depending on your point of view...)

We (as an organisation) changed the name of the original Story Points Custom Field to something else. We used that renamed field for a while and forgot we ever changed the name of the field. We then started wondering why we were using that weirdly named field and phased out its use in favor of a new Custom Field we created named Story Points... And that's why the Story Points field does not work but that other weird field works...

How funny...

Now starts the tedious process of copying all the SPs back to the original field and changing its name back to Story Points. I can't wait to do that... sad

Thanks again

unknown

Hi again,

I was wondering how Portfolio chooses the Custom Field ID of the Story Points. A quick search on the web shows that different people seem to have different IDs for the Story Points field. Hence, how does Portfolio choose? Is it possible to tell Portfolio which ID to use? And for that matter, is it possible to tell Agile which field to use as the default Story Point field?

Thanks for your help!

Nic

Steve Behnke [D1

I know that JIRA Agile/Software refers to the associated fields in the database. Portfolio could lift that data or determine it on it's own, but database modification is difficult.

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-software

jira-administration

advanced-roadmaps