Are there any steps beyond the documentation to using default estimates?

[Shane Fry]

I'm pulling in a single board to a live plan and trying to use default estimates.  I follow the documentation and go to the configuration>scheduling>unestimated item scheduling and select "base on default estimates" setting story, epic and initiative to 3, 8, and 40 respectively (just as listed in the documentation online).  When I return to the plan I do not see any of the estimates updating and am still receiving the warning "This issue is not appearing in the schedule. This may be because: This issue isn't scheduled because it hasn't been estimated".  

I've refreshed the page. I've recalculated the plan.  No luck.  Am I missing something?  I've searched other posts, questions and the open issues.  I don't see anyone else stating they are having this issue.  I'm using Server 2.13.1.

Any help is appreciated!

[Bhushan Nagaraj]

Hey Christopher,

A few reasons why you might be facing this issue has been listed at https://community.atlassian.com/t5/Jira-questions/Issues-not-showing-up-in-Portfolio-Live-Plans/qaq-p/108507

Please take a look and let me know if any of those fixed the issue.

[Shane Fry]

Thanks for the response Bhushan!  That was not my issue.  The stories are there but not showing the default estimate.

I figured it out.  I was setting story points to ‘0’ as a default value in JIRA when an issue is created.  I did it so that it could be seen from the issue screen and changed there versus having to open the edit screen.  I didn’t realize that 0 is an estimate in Portfolio.  Once I went in and changed the story point field to empty in JIRA then is set the default value as prescribed in Portfolio.

 I will say I was a little confused because while Portfolio wouldn’t set the default value because a number (0) was in the field, the warning message stated that it wouldn’t schedule because there was no estimate.  It seems to indicate that ‘0’ isn’t an estimate, but it won’t set a default.  I didn’t see anything in the online documentation referencing that little nuance, though I could have missed it.  Regardless, all good now. 

Again, really appreciate you trying to help.