I have defined the following calculated member within my EazyBI cube generated from my live JIRA software Cloud instance. The problem is that this MDX times out (takes longer than 60 seconds).
I am trying to find out how many issues have an estimate entered.
Is the problem that I am filtering against all issues? I thought that the filter would only work in the context of the dimension which the calculated member is called?
[Measures].[Original estimated hours] > 0
How can I restrict the filters or indeed use any other optimising technique in MDX to help this complete.
Any help appreciated since this is quite a simple thing which is proving very time consuming to work out how to do.
Indeed, this code goes through all Issues within selected report context.
In order to make it work faster, you could try adding an additional line in the code that filter the scope for search and it would search database column "Issues created" for all issues.
Count( Filter( Descendants( [Issue].CurrentMember, [Issue].[Issue]), [Measures].[Issues created]>0 AND [Measures].[Original estimated hours] > 0 ) )
Another thing you could try is to include such code in Case when.
If you use this calculated measure in the same query to calculate other calculated measures that depends on it, you could try using Cache.
Please contact email@example.com if you have further questions regarding this!
Martins Vanags / eazyBI
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...attest to the experience of an urgent approval that gets lost in the boss’s inbox and requires that special “Please Approve” email or text message. In an age where we have distributed teams...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs