Remaining Estimated Hours History for Epics including Linked Issues

Questions & Answers
, , , ,
1

Hello!

I’ve been using eazyBI for some time, but those measures are still defeating me…

I have this report which is counting the Remaining Estimated Hours History for all Epics and their Linked Issues (Issues in Epic). The Epics must have some properties (a specific fix version, a specific responsible team and the visualization to be for a specific time frame). The Epics part is quite simple (see image below), but the linked issues part…

image
image1008×635 45.5 KB

I’ve tried several times, but I still cannot include the Remaining Estimated Hours History for Linked Issues (Issues in Epic)… The linked issues do not have any of those filters. Looks like my filters (Fix Version, Issue Type) are also filtering out the linked issues from the report (as the linked issues do not met any of the selected filters). I’ve tried to remove the issue type and fix version filters and using the calculated measure below, but it’s extremely slow and doesn’t work anyway (I didn’t even add the responsible team filters as this is not working anyway…).

-- Relevant Epics
IIF(
  [Issue Type].[Issue Type].CurrentMember.Name = "Epic"
  AND
  ([Fix Version].[SpecificFixVersion], [Measures].[Issues created]) > 0,
  1,
  NULL
)


-- Remaining Estimate For Epics
Sum(
  Filter(
    Descendants([Issue].CurrentHierarchyMember, [Issue].[Issue]),
    (
      -- The issue is a Relevant Epic
      [Measures].[Relevant Epics] > 0
    )
    OR
    (
      -- The issue has an Epic Link to a Relevant Epic
      NOT IsEmpty([Issue].CurrentMember.Get('Epic Link'))
      AND
      (
        [Issue].[Issue].GetMemberByKey([Issue].CurrentMember.Get('Epic Link')),
        [Measures].[Relevant Epics]
      ) > 0
    )
  ),
  [Measures].[Remaining estimated hours history]
)

Does anyone has any idea how can I achieve this?

Thank you!

2

Hi @Flavius225 ,

The page filters and the report context work on measures. However, the values for measures are aggregated through hierarchies from the lowest hierarchy level.
When you apply the page filter for some specific Fix version, Team, or Issue Type - the values are aggregates from the issues related to the specific dimension combinations.

In case of Epic issue type, this only takes Epics as standalone issues and not their child stories.

The Fix version can be inherited as a linked issue field dimension as described here - Issue link field dimensions.

However, the responsible team has to be inherited as an epic level customfield as described here - Epic level custom field.

That will allow filtering child issues by the categories of their epics.

Regards,
Oskars / support@eazyBI.com

1 Like