Automation [Company Managed \ Classic]- roll up and sum story point estimates from stories to epics

[Neil Wills]

With our Classic project, we are estimating Epics to aid planning.

We are populating the field story point estimates, I am using and trying to edit the epic field story point estimates after summing up the story point estimates for each story.  The field on the epic is missing in the automation UX

{{lookupIssues.Story point estimate.sum}}

I believe this is intentional.

[Bill Sheboy]

Hi @Neil Wills 

Company-managed projects use the Story Points field and team-managed ones use the Story point estimate field.  Please try looking for the other one to see if that helps.

Kind regards,
Bill

[Neil Wills]

We are working with the team to point stories using Story points, and I have them rolling up to Story Points on the Epic.

If I used another field for the initial sizing with the team leads and product, we would be in a place where we can estimate the epics, make quarterly plans, and also compare the lead estimates with the team when we finally work the stories.

My plan was to roll up the initial high level estimates, and then during the refinement at a later phase before we enter the sprint that I can roll up the story points to the epic also. 

I didnt want to reuse story points field for both exercises as I would lose the initial estimates, that we could use to learn from the insights.

[Bill Sheboy]

Gotcha, and thanks for explaining.  You may want to consider using a separate custom field to hold that initial sizing in the epic, so you can fully manage it. 

The decision by Atlassian to use two separate story point fields (among other ideas) for company versus team-managed projects has caused quite a few issues.  If they ever decide to solve that in a way that consolidates the fields, your solution of using both fields could be impacted.  Using a separate custom field could prevent that.