Epic Size versus Accumulated Story Size

We would like to use the “Story Points” of an Epic as an estimate for the size of the Epic, and then compare that to the “Story Points History”. We have a burn-up timeline showing the “Story Point History” for “User Stories” but would like to have a separate measure for “Epic Story Point History” which only includes the size of the epics. Similarly we want a measure that doesn’t include the size of the epic, so we can determine how well our initial estimate matched the as implemented result.

We’re using “Projects”, “Fix Version” and “Issue Type” as pages and currently limited the “Issue Type” selection to “User Story”, “Task” and “Bug”. If we add “Epic” it calculates the history correctly, but we want to separate the epic history on a separate line.

Is there a way to calculate “Story Point History” for “Epics” only, even when the page view is limited?

Hi Lennon,

To get a measure value for some particular dimension member combination you would use Tuples, see more here https://docs.eazybi.com/eazybi/analyze-and-visualize/calculated-members#Calculatedmembers-Tuples.

For example, the following tuple in a new calculated Measure would return Story points history for Epic issue type

  [Measures].[Story Points history],
  [Issue Type].[Epic]

All other report context, like selected Fix Version and Projects, is still taken into account, only the Issue Type is overridden in this calculation. In the standard Story points history measure the report context will be fully taken into account and it will still show Story points history for the Issue Types selected in Pages.

Lauma / support@eazybi.com