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

Portfolio for Jira Cloud Unestimated Items not populating from default

Jason Baab

We are using Portfolio for Jira (cloud) and are experiencing an issues regarding unestimated items. He wave new boards in new projects and have many issues from Jira that are not yet estimated. When we use Portfolio, only those issues with story point estimates are showing on the roadmap (unless using "Target Schedule"). I have the parameter for Unestimated Item Scheduling set to Base on Default Estimates. I have the following values set: Story - 3, Epic - 8, Initiative - 40. However, I cannot get the default story points to apply to unestimated items.

Accepted answers

Earl McCutcheon

Hello Jason,

If the 'Unestimated item scheduling' set to 'Base on default estimates', the values should show up greyed out in the scope.

A bit of clarification though, are the values just not showing up at all, or are you showing values, that are not what you are expecting i.e. the 8 and 40 for the epic and initiative level, as if there is a value present in a child issue the value is summed up to the parent. So if you had a initiative with a child epic that contained a single story, the roll up would be 3 at the initiative hierarchy level.

Next double check if it's the system 'Story Points' field being used and not the 'Story point estimate' for next gen projects or possibly a secondary custom field called 'story points'. This will show up in the scope view settings menu and the system default 'Story Points' field should be the second from the top just under releases like this:

Screen Shot 2019-03-12 at 11.17.42 AM.png

And if you had additional custom fields added they would be lower on the list like this:

Screen Shot 2019-03-12 at 11.20.01 AM.png

Regards,
Earl

All comments

Earl McCutcheon

Hello Jason,

If the 'Unestimated item scheduling' set to 'Base on default estimates', the values should show up greyed out in the scope.

Screen Shot 2019-03-12 at 11.17.42 AM.png

And if you had additional custom fields added they would be lower on the list like this:

Screen Shot 2019-03-12 at 11.20.01 AM.png

Regards,
Earl

Jason Baab

Thanks for the response Earl!

To clarify, any issue that is not story pointed in Jira shows as "0" in Portfolio. I checked the field showing in Scope is "Story Point" as you have shown.

Any issue that is story pointed in Jira does carry over and rolls up from child to parent.

Thanks for your input!

Earl McCutcheon

Hi Jason,

Thanks for that additional info, and it sounds like what is occuring is that the field has a value present of "0" and is not null (empty), so effectively the value of "0" is taking priority over the default values that only populate if the field is left blank.

if you select the field and clear the 0 with a delete or backspace, does the default value populate?

Regards,
Earl

Jason Baab

Earl,

You are right - when I click in the Story point of a Story and delete the value, hit ENTER and the Story Point changes to the default (3).

Is there a way to "bulk" change these in Portfolio or must I do then all individually?

Thank you so much for your help!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

advanced-roadmaps