You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
With reference to an old discussion here: https://community.atlassian.com/t5/Jira-questions/EazyBI-How-to-filter-so-I-only-see-a-subset-of-a-dimension/qaq-p/15038
I've been using this technique for a while now. In my latest report for a different purpose, I have run into a puzzling snag with this. I'm basically trying to aggregate certain transitions and summing the "days in transition status" measure. I'm trying to sum up all the transitions that end with "Test Ready". Here is what I have used:
Aggregate({
Generate(Filter(NonEmptyCrossJoin(
Descendants([Transition].CurrentMember, [Transition].[Transition]),
[Measures].DefaultMember),
trim([Transition].CurrentMember.Name) MATCHES '.*Test Ready$'),
[Transition].[Transition].CurrentMember )
})
My input "data set" is:
Open => Test Ready
In Progress => Test Ready
Reopened => Test Ready
Resolved => Test Ready
In Review => Test Ready
Refining => Test Ready
Integration Test Prep => Test Ready
Test Ready => Test Ready
Testing => Test Ready
Ready For Release => Test Ready
Ready => Test Ready
Committed => Test Ready
The MDX logic is picking up 9 of the above, except for these three:
Resolved => Test Ready
Refining => Test Ready
Ready For Release => Test Ready
Why would the pattern match everything else but these three? I've almost gone insane trying to figure out what's wrong. And I am sure it's something pretty silly that I have missed. Can someone help please?
Hi,
The formula looks correct, indeed. A bit more compact version should do the same:
Aggregate({
Filter([Transition].[Transition].Members,
trim([Transition].CurrentMember.Name) MATCHES '.*Test Ready$')
})
Note that eazyBI creates only those members in the dimension having any corresponding measures. In other words, eazyBI create transitions if those are present in the imported data set.
If that does not explain the problem, please, put a support ticket. The report definition will be needed.
Kindly,
Janis, eazyBI support
It looks like it's alright.
I would just type in all the transitions if you are still having issues. Not ideal, but it will work.
Regards,
Fabian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.