Hi @vpurho,
If you are using a common sprint naming convention, you might import additional property for the sprints using Additional data import into Issues cube and then create a custom hierarchy within the Sprints dimension based on that property.
Please read more about additional data import here -Additional data import into Jira Issues cube.
Please read more about creating custom hierarchies here - Custom hierarchies.
This would group sprints into categories in a similar way as boards. You might then iterate through sprints from these categories.
Please read more about this approach here - Aggregate Sprint By Name - #2 by zane.baranovska.
The new way of finding the last 5 closed sprints within each category might be as follows.
Aggregate(
Generate(
--for each of categories
[Sprint.<hierarchy name>].[<hierarchy top level name>].Members,
Head(
Order(
Filter(
DescendantsSet(
--descend from the category
[Sprint.<hierarchy name>].CurrentMember,
--to the level of sprint
[Sprint.<hierarchy name>].[Sprint]),
--filter only closed sprints
[Sprint.<hierarchy name>].CurrentMember.GetBoolean('Closed')),
--order by closure date
[Sprint.<hierarchy name>].CurrentMember.Get('Complete date'),
DESC),
--take the last 5 items from ordered set
5)
)
)
Regards,
Oskars / support@eazyBI.com