Hi
I am using EazyBi 7.1 with Confluence 8.5.18 and the ‘eazyBI dashboard’ Macro (not sure which version)
I have a dashboard that exhibits a strange behaviour in the filer drop down.
What happens for one of the reports is that when I click on the drop down for a filter the drop down opens but then pretty much immediately closes again. This happend for all filters in that report.
the strange thing is that I have another report on the same dashboard that has similar/same filters that does not have that issue.
I already tried to remove the report from the dashboard and add it again. → same behaviour
If I open the Dashboard in EazyBi then the issue doesn’t exist.
So issue relates to 1 report when displayed in Confluence.
Same report works fine on the same Dashboard in EazyBi.
Any idea how to fox this???
Cheers Ralph
Update:
This seems to be related to the GANNT view. I switched the report from GANNT to table view and it works as normal.
Currently trying to recreate the report to see if it’s a specific bug in the report
Hi @ralph.warta
You might want to try upgrading eazyBI version and then try again.
We did some some changes recently with gantt charts in one of the recent versions.
If you can repeat the problem on the 8.2 version, please export and share the definition with support@eazybi.com so we can check what might have caused this behavior in your report.
Martins / eazyBI
Hi
i think I found the issue
I had a MDX in my Issue Type Dimension (see below). I only wanted to see the Issue Types that are used in my data set (and cube). It seems when this was selected for the Issue Type Dimension in pages that the report threw error or showed no data. I suspect its because I also had issues created in columns…?
is there a more robust way to do this? Can I tell EazyBi always to only show the issue types that are actually in the cube?
Cheers Ralph
– Aggregate of issue types that have at least one issue created
Aggregate(
Filter(
[Issue Type].[Issue Type].Members,
[Measures].[Issues created] > 0
)
)
@ralph.warta
We usually do not recomment creating aggregates with filters that use context measures (such as “Issues created” in filter conditions).
That should be done when creating calculated measures
Note that “Issue type” is a default dimension in the eazyBI “Issues” cube and it imports also historical issue types for the issues that you import in the “Issues” cube.
Why don’t you instead consider importing a new account-specific calculated field “Current issuetype”, which would let you importa new dimension with members just from the current issue types.
Then you can use this dimension in your reports and it shouldn’t show issue types that do not exist in the issues anymore.
Martins / eazyBI
@martins.vanags thanks yes that would work. Would be great though if EazyBi does that OOTB in the IssueType dimension. Assume I am not the only one who filter out certain issue types on import (using the JQL filter) and therefore only wants to see the used ones
1 Like