Create a view with Epic and thier children issues filtered on Epic components

Questions & Answers
2

Hi @PRL ,
​
​Since the compoent is a multi-value field - it cannot be inherited from parent issue to children and grandchildren.
​In this case, you would need to use the Ancestor() function to reach out for the Epic standing above in the hierarchy and return the result if the condition is fulfilled.
​
​Please read more about the Ancestor() function here - Ancestor.
​
​The construction might be as follows.
​

CASE WHEN
--condition to avoid error for the "All issues" level when there are no Epic ancestors
 NOT [Issue].CurrentHierarchyMember is [Issue].CurrentHierarchy.DefaultMember
--optional extra clause for condition if Initiative exists on top of Epic in this hierarchy
-- AND
-- NOT [Issue].CurrentHierarchyMember.Level.Name = "Initiative"
THEN
 CASE WHEN
--checking Epic relevance to the report context - filters etc.
  ([Measures].[Issues created],
--reach up within hierarchy
   Ancestor(
--the start point for climbing up the hierarchy
    [Issue].CurrentHierarchyMember,
--destination level for climbing up the hierarchy
    [Issue].CurrentHierarchy.Levels("Epic")),
--limit issue type to only check the Epic relevance
   [Issue Type].[Epic])>0
 THEN
  <primary calculation to be done at the individual issue level - expression to be displayed>
 END
END

Regards,
​Oskars / support@eazyBI.com​
​