Hi guys!
@thv
There are several ways how to use the Descendants function when you need to access properties from lower-level members. For example, in your use case, you could try to iterate through the Sprint dimension instead of the Issue dimension, like in this solution: Roll up sprint start and end dates from stories to epic on gantt chart - #2 by janis.plume
Also, when using the Issue dimension in the report, it is important to enable the “Nonempty” option in the Rows section and use at least one real measure in the report (not just properties). Additionally, you can check out this video by Daina on all the small details that can be improved in a report (these details are increasingly important as account size increases): Help, My Reports Are Too Slow!
As the MDX queries in eazyBI give the user a lot of freedom to get the same result in different ways, it is often important to understand if the optimal formula/approach is used. In these cases, we invite you to reach out to us at support@eazybi.com to understand and possibly fix the slow reports. When reaching out, you can also export and add your report definition/screenshots/log files to the email so we can better assess the current situation.
@Jade
I understand the frustration with slow reports, and it is indeed the case that the larger the data set gets, the more time it will take to cross-examine and return results for your queries in a report.
In these cases, we would like to encourage you to use the (usage statistics) feature to pinpoint the slow reports and reach out to us with the details. If this is an account-wise problem, we can help you revise your source import options, if this is an instance-wise problem, then you can send us the log files to check out what is happening in the background. Sometimes insufficient memory, lack of a dedicated node or some other issue can be a bottleneck for the set-up.
Looking forward to helping out in each of your individual cases!
Best regards,
Nauris