I have a report where I showing rows by Issue → Parent → Hierarchy Level 4 (which are Initiatives in our Jira Issue Hierarchy). I would like to be able to filter where only that hierarch level, Initiatives, has a particular component.
If just add components in Page Filters and select the Component, it applies to all results (not surprising) and my counts for child cards under each Initiative card are much lower.
My assumption is that I need to add a new calculated member under Page Filter → Component but I’m not sure of how I make it apply only to card types that equal Initiatives and not any other types.
It would only let me put in one image, so here are the before and after results when I just select a component from Page Filters without doing anything special
Hello @david.foote ,
The component field is a multi-value field and thus is unavailable to be imported as issue linked field dimension, but you can use a similar approach that was suggested in this answer:
See the adjusted formula below that uses the component dimension, and hierarchy levels like this:
CASE WHEN
-- avoid error when at "All issues" level
NOT [Issue].CurrentHierarchyMember is [Issue].CurrentHierarchy.DefaultMember
AND
-- skip Improvement level if it exists
NOT [Issue].CurrentHierarchyMember.Level.Name = "Improvement"
THEN
CASE WHEN
-- check if Feature ancestor has issues
([Measures].[Issues created],
-- get Feature ancestor in hierarchy
Ancestor(
[Issue].CurrentHierarchyMember,
[Issue].CurrentHierarchy.Levels("Feature")
),
[Component].CurrentHierarchyMember,
[Issue Type].[Feature])>0
THEN
-- Reset Component context to default to get total across all components, use the formula you need
([Measures].[Issues resolved],
[Component].CurrentHierarchy.DefaultMember)
END
END
Also, to avoid that hierarchy levels are imported as Hierarchy Level 4, Hierarchy Level 3 etc, you can add additional advanced settings with the Parent hierarchy nams so they match the level names used in Jira, see more here: Plans custom fields
