Cannot get sum of the Jira Issues.’Story Point’ rows in a Card to change with slicer filter

[timoparks]

Hi, we are having trouble trying to sum or total the Jira  Issues.’Story Point’  field for a group of issues and see it’s total change when we apply a slicer in PowerBI Desktop. The field is a number. We find that when we use the total for Issues.’Story Point’ in a Card in PowerBI it only shows the total story points for all unfiltered items. Ignoring any filters by applying slicers.

We have tried using a measure, but this does not change in the Card when we apply slicer filters.

CountStoryPointInRelease = SUM(Issues[Story_Points_10031])

Can you help? Thanks T.

[cengizhanarslan]

Seems like  your slicer table is not related to fact table or edit interactions are turnef off in the report view.

[sergej_og]

Hi @timoparks ,
your model is connected properly?
Dimensions are connected with the fact(s)?
Sounds a bit like missing connections between the tables.

Regards

[timoparks]

Thanks for the replies and support.

It is definitely a data model relationship problem as was suggested. But I still have not been able to fix it.

I ‘m try to total the “Story Points” field of all matching rows in the Issues table.

A slicer filter on data in the Issues table works fine and gives a correct total.

But using a Slicer with data from the IssueFixVersions table has no effect even though the is a 1-to-Many relationship from Issues.Issue_id to IssueFixVersions.Issue_id

Thanks

T.

[sergej_og · Accepted solution]

Hi @timoparks ,
looking at your model I can see 1:* between Issue (1) and IssueFixVersion (*), the filter direction is from Issues to IssueFixVersion (single). If you are trying to filter Issues with a field from IssueFixVerison this is not going to work due to missing filter direction. Meaning IssueFixVersion isn't able to filter Issues.
Either you create a proper "dim_issues" table (= a dimension table) or you set the cross-filter direction to BOTH between these tables.
I guess setting the filter direction is going to help you for the moment.

I think it makes sense to rethink the modelling part a bit.

Give it a try?

Regards