I’m creating a sprint velocity chart using the eazy BI sample report. When I select a particular board in the Sprint dimension, it does not show all the sprints belonging to the board. When I expand the selection under the board, I only see two sprints (future sprints) but not any of the old sprints. The velocity chart in Jira works OK so it shows the previous sprints. And the sprints have been created on that board in Jira as well.
If I search the sprints with sprint name in the Select individual members, I can see the sprints in the list but for some reason they don’t seem to appear under the board. If I select some other board, it works OK. The data is only from one project and the project has multiple boards.
Any ideas for the cause of this and how to resolve?
So I have to create calculated members to find all sprints with the sprint name.
This is the code I’m currently using:
Aggregate(
Order(
Filter(
[Sprint].[Sprint].Members,
Left([Sprint].CurrentMember.Name, 6) = “MDM PI” AND
[Sprint].CurrentHierarchyMember.GetBoolean(‘Closed’) AND
DateBetween(
[Sprint].CurrentMember.get(‘End date’),
‘12 months ago’,
‘Now’)
),
[Sprint].CurrentMember.GetDate(‘Start date’),
BASC
)
)
I tried to make this work so that it would take the five latest closed sprints based on sprint closing date but could not get it work, but this is OK for now.
But this also brings out an issue with using some of the standard measures like Running story points velocity of 5 closed sprints which does not work as it assumes that the sprints are in one board.
Is there a way to create a calculated measure that would utilise the calculated members to achieve the same result?
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.
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)
)
)