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
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.
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...
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...
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!
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG